Loading vulnerability…
CVE-2019-9760 affects FTPGetter Standard version 5.97.0.177. The vulnerability is triggered when a user initiates an FTP connection to an attacker-controlled FTP server that returns crafted protocol responses. According to the provided description, specially crafted long responses can corrupt memory in the FTP client, leading to application instability and potentially remote code execution. The issue is therefore a client-side memory corruption flaw reachable through malicious server responses during an FTP session.
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 exploit module targeting a stack buffer overflow vulnerability in FTPGetter Standard v3.55.0.05 (CVE-2019-9760). The exploit works by running a malicious FTP server that delivers a specially crafted response to the PWD command, causing a buffer overflow in the client and allowing arbitrary code execution via an egghunter payload. The module is written in Ruby and leverages Metasploit's FtpServer and Egghunter mixins. The exploit is operational and allows the attacker to execute custom payloads (such as reverse shells) on the victim's Windows XP SP3 system when the vulnerable FTP client connects and issues a PWD command. The only file present is the Metasploit module itself, and there are no hardcoded network endpoints or IP addresses, as the attack is performed by the server hosting 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.