Loading vulnerability…
EzServer 6.4.017 improperly handles an excessively long string supplied to the RNTO command. Processing the oversized command input can crash the EzServer daemon, causing a denial of service.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/windows/http/ezserver_http.rb) that exploits a stack buffer overflow vulnerability in EZHomeTech EZServer versions 6.4.017 and earlier (CVE-2024-23985). The exploit targets the service running on TCP port 8000 (default) on Windows XP. It uses the egghunter technique to deliver and execute arbitrary shellcode, bypassing buffer size constraints. The module is operational and allows the attacker to execute code of their choice on the target system. The code is written in Ruby and follows the standard Metasploit module structure, including references, target definitions, and payload handling. No hardcoded IP addresses, URLs, or file paths are present; the only fingerprintable endpoint is the TCP port 8000. The exploit is not a detection script or a fake, and is suitable for use in penetration testing or red teaming engagements.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.