CVE-2012-10030 affects FreeFloat FTP Server and stems from multiple insecure design and access-control failures in the FTP service. The server accepts empty credentials for authentication, places users at the root of the C:\ drive by default, and does not adequately restrict upload destination paths or file types. As a result, an unauthenticated remote attacker can upload arbitrary files directly into sensitive Windows directories, including locations such as C:\Windows\System32 and C:\Windows\System32\wbem\mof. By uploading executable payloads or specially crafted .mof files into WMI-monitored directories, the attacker can trigger automatic processing by Windows Management Instrumentation, leading to remote code execution. Because the affected directories and WMI processing occur in a highly privileged context, successful exploitation can result in code execution with SYSTEM-level privileges and requires no user interaction.
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 (Ruby file) that exploits multiple security flaws in the FreeFloat FTP Server for Windows (CVE-2012-10030). The exploit leverages the lack of authentication and unrestricted file upload capabilities of the FTP server to upload a malicious Windows executable and a MOF file. The MOF file is placed in the WMI directory, causing the Windows Management Instrumentation service to execute the uploaded payload with system privileges. The module is operational and allows the attacker to execute arbitrary code on the target system. The exploit is network-based, targeting the FTP service, and does not require valid credentials. The main fingerprintable endpoints are the file paths where the payload and MOF file are uploaded. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single Ruby file.
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.
4 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.