Seagull FTP Client <= v3.3 Build 409 contains a stack-based buffer overflow vulnerability in its FTP directory listing parser. When the client connects to an FTP server and receives a crafted response to a LIST command containing an excessively long filename, the application fails to properly validate input length, resulting in a buffer overflow that overwrites the Structured Exception Handler (SEH). This may allow remote attackers to execute arbitrary code on the client system. This product line was discontinued and users were advised to use BlueZone Secure FTP instead, at the time of disclosure.
Security readout for executives and security teams
Plain-English summary
CVE-2010-20007 is a high-severity flaw in the discontinued Seagull FTP Client. A malicious FTP server response can crash or potentially take control of the client when a user connects and the directory listing is parsed. Business risk is mainly legacy desktop exposure, not internet-facing server exposure.
Executive priority
Prioritize removal if the client exists. The issue is old, public, and affects a discontinued product, so patch confidence is weak. The practical decision is usually migration or retirement, especially on privileged workstations.
Technical view
Seagull FTP Client up to v3.3 Build 409 has a stack-based buffer overflow in its FTP LIST directory listing parser. An excessively long filename in a crafted server response can overwrite SEH and may allow arbitrary code execution on the client. User interaction is required because the client must connect to the FTP server.
Likely exposure
Exposure is likely limited to organizations still running Seagull FTP Client v3.3 Build 409 or older. The product line was discontinued, so unmanaged legacy workstations, old jump boxes, or file-transfer workflows are the most plausible locations.
Exploitation context
Public exploit references exist, including Exploit-DB, Metasploit, and Corelan material. The source bundle does not show CISA KEV listing or confirmed active exploitation. Treat it as publicly weaponized but not source-confirmed as actively exploited.
Researcher notes
The key uncertainty is current deployed footprint. Sources support a client-side LIST parser overflow with SEH overwrite and public exploit material. Do not assume active exploitation from the provided evidence; KEV is false in the bundle.
Mitigation direction
Inventory endpoints for Seagull FTP Client v3.3 Build 409 or older.
Remove or replace Seagull FTP Client where found.
Check Rocket or BlueZone guidance for supported migration options.
Block legacy clients from connecting to untrusted FTP servers.
Apply compensating controls for any system awaiting replacement.
Validation and detection
Search software inventory for Seagull FTP Client installations and versions.
Review file-transfer workflows that still require FTP client software.
Confirm whether users can launch the discontinued client.
Check endpoint telemetry for Seagull FTP process execution.
Document any exceptions with owner, business need, and retirement date.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.