Loading vulnerability…
CVE-2010-20049 is a stack-based buffer overflow in LeapFTP versions prior to 3.1.x. The flaw is in the FTP client’s parser for directory listings: when LeapFTP processes a filename longer than 528 bytes returned by an FTP server, it does not properly validate or bound-check the input before copying it into a fixed-size stack buffer. This results in memory corruption and can overwrite the Structured Exception Handler (SEH) chain. A remote attacker controlling a malicious FTP server can trigger the vulnerability when the victim connects and the crafted directory entry is listed or when the file is downloaded, leading to 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 that exploits a stack buffer overflow vulnerability in the LeapFTP 3.0.1 client for Windows (CVE-2010-20049). The exploit works by running a malicious FTP server that, when accessed by a vulnerable LeapFTP client, sends a specially crafted directory listing containing a file with an overly long name. This triggers a buffer overflow in the client, allowing arbitrary code execution. The module uses an egghunter to locate the payload in memory and supports customizable shellcode. The main attack vector is network-based, requiring the victim to connect to the attacker's FTP server. The only fingerprintable endpoint is the fake filename used in the directory listing, which is designed to exploit the vulnerability. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.