Loading vulnerability…
A buffer overflow vulnerability exists in Labtam ProFTP version 2.9, where the application fails to properly handle excessively long 220 reply messages (FTP connection greetings) sent by remote FTP servers. This flaw allows a malicious FTP server to send a crafted welcome message that overflows a buffer in the client, potentially leading to application crash or arbitrary code execution.
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 buffer overflow vulnerability in the ProFTP 2.9 client (CVE-2009-3976). The exploit works by running a malicious FTP server that sends an overly long welcome banner to the connecting client. When a vulnerable ProFTP 2.9 client connects, the crafted banner overflows a buffer, allowing the attacker to execute arbitrary code on the client system. The module is written in Ruby and leverages the Metasploit framework's TCP server capabilities. The payload is customizable and can be any Metasploit payload fitting within the 1000-byte space, avoiding certain bad characters. The only network endpoint is the attacker's server, which listens on TCP port 21 (the standard FTP port). The exploit is operational and can be used to gain code execution on vulnerable clients.
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.