A buffer overflow vulnerability exists in LeapFTP 2.7.3.600, where a remote FTP server can send an excessively long IP address in response to a PASV command, causing a buffer overflow and allowing execution of arbitrary code 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 (1 hidden).
This repository contains a single Metasploit module targeting a buffer overflow vulnerability (CVE-2003-0558) in LeapWare LeapFTP v2.7.3.600 for Windows. The exploit works by running a malicious FTP server that sends an overly long PASV reply to the client, triggering a buffer overflow and allowing arbitrary code execution. The module is written in Ruby and leverages Metasploit's TcpServer and SEH exploitation mixins. The payload is customizable (up to 1000 bytes) and avoids specific bad characters. The exploit targets LeapFTP clients running on Windows 2000 (SP0/SP4) and Windows XP (SP0). The only network endpoint is the attacker's FTP server, which listens on TCP port 21. The repository is operational and provides a working exploit for the specified vulnerability.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.