A stack-based buffer overflow vulnerability exists in CesarFTP 0.99g and earlier, triggered by sending an overly long argument to the MKD command. This can cause the application to crash and may allow remote attackers to execute arbitrary code. The vulnerability is due to improper bounds checking when handling the MKD command input.
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 (2 hidden).
This repository contains a single Metasploit module (Ruby file) that exploits a stack buffer overflow vulnerability in the MKD command of CesarFTP 0.99g (CVE-2006-2961). The exploit targets Windows 2000 Pro SP4, Windows XP SP2/SP3, and Windows 2003 SP1 systems running the vulnerable FTP server. The attacker must have valid FTP credentials to trigger the vulnerability. The exploit works by sending a specially crafted MKD command to the FTP service (default TCP port 21), causing a buffer overflow and allowing execution of arbitrary code with the privileges of the FTP process. The payload is customizable via Metasploit and can be any compatible shellcode (reverse shell, meterpreter, etc.). The module includes checks for the target banner to verify the presence of CesarFTP 0.99g. The code is operational and ready for use within the Metasploit framework.
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.