Loading vulnerability…
CVE-2009-1675 is a stack-based buffer overflow in ElectraSoft 32bit FTP 09.04.24. The flaw is triggered when the FTP client processes an overly long 227 reply from a remote FTP server in response to a PASV command. Because the client does not properly bound-check the server-supplied reply before copying it into a stack buffer, a malicious FTP server can corrupt stack memory and potentially redirect execution flow. The vulnerability affects the client-side handling of FTP protocol responses rather than the server component.
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 exploit module targeting a stack buffer overflow vulnerability (CVE-2009-1675) in the 32bit FTP Client for Windows. The exploit works by running a malicious FTP server that, when accessed by a vulnerable client, sends a directory listing containing a file with a specially crafted, overly long filename. This filename includes custom shellcode and an egghunter, which, when processed by the client (typically when the user attempts to download the file), triggers the buffer overflow and executes arbitrary code. The module is written in Ruby and leverages Metasploit's FtpServer mixin to handle FTP protocol interactions. The payload is customizable via Metasploit's payload system, and the exploit is operational, providing code execution on the victim's machine. The only file in the repository is the exploit module itself, and it is structured according to Metasploit conventions.
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.