Loading vulnerability…
CVE-2010-20007 affects Seagull FTP Client through v3.3 Build 409. The vulnerability is a stack-based buffer overflow in the client's FTP directory listing parser. When the client issues or processes a LIST operation and receives a maliciously crafted directory listing entry containing an excessively long filename, the application does not properly validate the input length before copying it into a fixed-size stack buffer. This can corrupt stack memory and overwrite the Structured Exception Handler (SEH), creating a path to arbitrary code execution on the client system.
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/seagull_list_reply.rb) that exploits a stack buffer overflow vulnerability in the Seagull FTP client v3.3 Build 409 (CVE-2010-20007). The exploit works by running a malicious FTP server that delivers a specially crafted response to the LIST command. When the vulnerable client processes this response, a buffer overflow occurs, allowing the attacker to overwrite the Structured Exception Handler (SEH) and execute arbitrary code. The module uses Metasploit's Omelet mixin to split the payload into 'eggs' and reconstruct it in memory, bypassing size restrictions. The payload is customizable and can be any Metasploit-supported Windows shellcode. The exploit targets Windows XP and requires the victim to connect to the attacker's FTP server and issue a LIST command. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.