Loading vulnerability…
CVE-2010-10014 affects Odin Secure FTP version 4.1 and earlier. The client is vulnerable to a stack-based buffer overflow while parsing directory listings returned by an FTP server in response to a LIST command. A malicious server can include an excessively long filename in the directory listing, causing a fixed-size stack buffer in the client to overflow. The overflow can overwrite the Structured Exception Handler (SEH), creating a path to controlled execution flow and arbitrary code execution on the client system.
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 exploit targeting Odin Secure FTP 4.1 on Windows. The exploit abuses a stack buffer overflow vulnerability triggered by a maliciously crafted response to the FTP LIST command. The module acts as a malicious FTP server; when a vulnerable client connects and issues a LIST command, the server responds with a specially crafted directory listing that overflows the stack, overwrites the Structured Exception Handler (SEH), and executes an egghunter payload. The egghunter locates and executes the main Metasploit payload, which can be customized (e.g., reverse shell, meterpreter). The exploit is operational and leverages Metasploit's payload and egghunter utilities. The only file present is the Metasploit Ruby module implementing this exploit. The main attack vector is network-based, requiring the victim to connect to the attacker's FTP server. The exploit specifically targets Odin Secure FTP 4.1 on Windows XP SP3, and is referenced by CVE-2010-10014.
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.