Gekko Manager FTP Client <= 0.77 contains a stack-based buffer overflow in its FTP directory listing parser. When processing a server response to a LIST command, the client fails to properly validate the length of filenames. A crafted response containing an overly long filename can overwrite the Structured Exception Handler (SEH), potentially allowing remote code execution.
Security readout for executives and security teams
Plain-English summary
A legacy FTP client can be crashed or potentially taken over when a user connects to a malicious or compromised FTP server. The weakness is in how Gekko Manager FTP Client handles long filenames in directory listings. This is serious, but exposure is likely limited to organizations still running this old client.
Executive priority
Treat as high priority only if the client exists in your environment. The business risk is endpoint compromise through a user workflow, but broad enterprise exposure is unlikely unless this legacy FTP client remains deployed.
Technical view
Gekko Manager FTP Client <= 0.77 has a CWE-121 stack buffer overflow in its FTP LIST response parser. An overly long filename in a server directory listing can overwrite SEH and may allow code execution in the client process. The supplied CVSS 4.0 score is 8.5 with user interaction required.
Likely exposure
Likely limited to endpoints with Gekko Manager FTP Client <= 0.77 installed, especially users who connect to external, unknown, or compromised FTP servers. The affected-version data in the bundle is inconsistent, so confirm exact installed versions before scoping.
Exploitation context
The bundle cites public exploit references, including Exploit-DB and Metasploit, so proof-of-concept or module-level exploitation knowledge exists. The CVE is not listed as KEV in the supplied data, and no source here confirms active exploitation in the wild.
Researcher notes
Use caution with version scoping: the title and description say <= 0.77, while the structured affected entry lists version 0. Public exploit references support exploitability, but the bundle does not prove current exploitation or identify a vendor patch.
Mitigation direction
Remove Gekko Manager FTP Client from managed endpoints where it is not required.
Replace it with a supported FTP/SFTP client maintained by its vendor.
Avoid connecting legacy clients to untrusted or internet-hosted FTP servers.
Isolate systems that must temporarily run the client.
Check vendor and advisory sources for any fixed release or official guidance.
Validation and detection
Inventory endpoints for Gekko Manager FTP Client installations and recorded versions.
Prioritize users who access external FTP servers or receive FTP connection details by email.
Review software allowlists and endpoint telemetry for legacy FTP client usage.
Confirm whether any business workflow still depends on this client.
Track advisory updates because source data does not name a patch.
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
6Source 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.