Loading vulnerability…
FTPShell Client 6.7 is vulnerable to a buffer overflow when processing an FTP 220 response containing 400 characters of 'F'. A malicious FTP server can exploit this by sending an overly long 220 response, causing the client to crash and potentially allowing arbitrary code execution on the victim's machine. This vulnerability is similar to CVE-2009-3364 and CVE-2017-6465, which also involve buffer overflows in FTP client/server interactions.
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 (modules/exploits/windows/ftp/ftpshell_cli_bof.rb) that exploits a stack buffer overflow vulnerability (CVE-2018-7573) in FTPShell client 6.70 (Enterprise edition) for Windows. The exploit works by running a malicious FTP server that delivers a specially crafted response to the client, triggering the overflow and allowing arbitrary code execution. The module is fully integrated with Metasploit, allowing the attacker to select and deliver a payload of their choice (up to 400 bytes, avoiding certain bad characters). The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The only network endpoint involved is the attacker's FTP server, which listens on a configurable IP and port (default 0.0.0.0:21). The repository is structured as a single Ruby file following Metasploit conventions, and its sole purpose is to provide a reliable remote code execution exploit for the specified FTPShell client vulnerability.
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.