A stack-based buffer overflow exists in the sreplace() function of ProFTPD versions 1.3.0 and earlier. The vulnerability is caused by an off-by-one error in string manipulation, allowing remote attackers with FTP write access to trigger a buffer overflow and execute arbitrary code. The flaw was exploited in the wild and included in the VulnDisco Pack for Metasploit as vd_proftpd.pm. The vulnerability was patched in ProFTPD version 1.3.0a.
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 (modules/exploits/linux/ftp/proftp_sreplace.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2006-5815) in ProFTPD versions 1.2 through 1.3.0 on Linux. The exploit works by uploading a specially crafted .message file to a writable directory on the FTP server and then triggering the vulnerable sreplace function by changing into that directory. The module supports automatic target detection based on the FTP banner and allows for custom payloads up to 900 bytes, with certain bad characters filtered. The exploit requires access to a writable directory (default: /incoming) and can provide remote code execution as a privileged user. The code is written in Ruby and is designed to be used within the Metasploit framework. Notable fingerprintable endpoints include the writable directory path, the .message file, and the '250' file (for certain ProFTPD versions).
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.