Loading vulnerability…
A buffer overflow vulnerability exists in SlimFTPd versions 3.15 and 3.16, where remote authenticated users can trigger a buffer overflow by supplying an excessively long directory name to the LIST, DELE, or RNFR FTP commands. This flaw allows for the execution of arbitrary code on the affected system, as the input is not properly validated before being copied into a fixed-size buffer.
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 exploit module targeting a stack buffer overflow vulnerability in SlimFTPd (CVE-2005-2373). The exploit is implemented in Ruby and is designed to be used within the Metasploit Framework. The vulnerability is triggered by sending an overly long argument to the FTP LIST command after logging in to the server. The exploit constructs a specially crafted buffer containing a customizable payload and the target's return address, then sends it via the LIST command to achieve arbitrary code execution. The module supports any Metasploit Windows payload, such as reverse shells or Meterpreter sessions. The only endpoint involved is the FTP service (typically TCP port 21) on the vulnerable SlimFTPd server. The repository is operational and ready for use within Metasploit, requiring only a vulnerable target and valid FTP credentials.
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.