A stack-based buffer overflow exists in VanDyke Software AbsoluteFTP versions 1.9.6 through 2.2.10. The vulnerability is triggered when a remote FTP server sends a crafted file name in response to a LIST command, causing the client to overflow a stack buffer and potentially allowing execution of arbitrary code.
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 (Ruby file) that exploits a remote buffer overflow vulnerability in VanDyke Software AbsoluteFTP versions 1.9.6 through 2.2.10.252 (CVE-2011-5164). The exploit works by running a malicious FTP server that sends a specially crafted response to the LIST command, overflowing a filename buffer in the AbsoluteFTP client. The module constructs a buffer containing ROP gadgets and a customizable Metasploit payload, enabling remote code execution on the victim's Windows system when they connect and issue a LIST command. The exploit targets Windows XP SP2 through Windows 7 SP1 and has been tested on a wide range of AbsoluteFTP builds. The code is operational and allows for arbitrary payloads to be delivered via the Metasploit framework. No hardcoded IPs, domains, or URLs are present; the attack vector is purely network-based, exploiting the FTP protocol and the LIST command's directory listing response.
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.