Loading vulnerability…
CVE-2010-20034 affects Gekko Manager FTP Client version 0.77 and earlier. The vulnerability is a stack-based buffer overflow in the client's FTP directory listing parser when handling a server response to the LIST command. The client does not properly validate the length of filenames returned in the directory listing. A malicious FTP server, or an attacker able to tamper with the server's LIST response, can supply an excessively long filename that overflows a stack buffer and overwrites the Structured Exception Handler (SEH), creating a path to code execution in the context of the client 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 exploit module targeting a stack buffer overflow vulnerability in the Gekko Manager FTP client (CVE-2010-20034). The exploit works by running a malicious FTP server that responds to a LIST command with a specially crafted filename in the directory listing. This filename overflows a buffer in the client, overwriting the Structured Exception Handler (SEH) and allowing arbitrary code execution via an egghunter payload. The module is written in Ruby and leverages Metasploit's FtpServer and Egghunter mixins. The payload is customizable and encoded to avoid bad characters. The exploit is operational and can be used to gain code execution on vulnerable Gekko Manager FTP clients connecting to the attacker's server. The only file present is the exploit module itself, and no additional endpoints or network addresses are hardcoded; the attack vector is purely network-based, relying on the FTP protocol.
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.