Loading vulnerability…
CVE-2010-20122 is a stack-based buffer overflow in Xftp FTP Client versions up to and including 3.0 build 0238. The flaw is triggered when the client processes a maliciously crafted FTP server response to the PWD command. An attacker-controlled server can return an overly long directory string, and the client does not properly validate the input length before copying it into a fixed-size stack buffer. This leads to memory corruption and can permit arbitrary code execution on the client system in the context of the user running Xftp.
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/xftp_client_pwd.rb) that exploits a buffer overflow vulnerability in the Xftp 3.0 FTP client (CVE-2010-20122). The exploit works by running a malicious FTP server that waits for a connection from the vulnerable client. During the FTP session, the server sends an overly long response to the PWD command, triggering a buffer overflow in the client and allowing arbitrary code execution. The module allows the attacker to specify a custom payload (up to 434 bytes, avoiding null and newline bytes), which is delivered as part of the malicious PWD response. The exploit targets Windows systems running Xftp 3.0 and requires the victim to connect to the attacker's FTP server. The code is written in Ruby and is structured as a standard Metasploit exploit module, using the Msf::Exploit::Remote::TcpServer mixin to handle incoming connections and deliver the exploit.
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.
2 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.