CVE-2012-10023 is a stack-based buffer overflow in FreeFloat FTP Server version 1.0.0. The vulnerability is caused by improper validation of input supplied to the USER command. By sending an overly long username string during authentication, a remote attacker can overflow a stack-allocated buffer and overwrite adjacent memory. This memory corruption condition can crash the service and, depending on exploitability and target conditions, may allow arbitrary code execution in the context of the FTP server process.
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 module (modules/exploits/windows/ftp/freefloatftp_user.rb) that exploits a stack-based buffer overflow vulnerability in Free Float FTP Server (CVE-2012-10023). The exploit targets the USER command, sending a specially crafted username to overflow the stack and execute arbitrary code. The module is weaponized, allowing the attacker to select a payload (such as a reverse shell) up to 444 bytes, which is delivered as part of the exploit. The exploit is designed for Windows XP SP3 running the vulnerable FTP server, and operates over the network via the FTP protocol (TCP port 21). The module includes a check method to verify if the target is running Free Float FTP Server by examining the FTP banner. The code is written in Ruby and follows the standard Metasploit module structure, making it easy to 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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.