Xftp FTP Client version up to and including 3.0 (build 0238) contain a stack-based buffer overflow vulnerability triggered by a maliciously crafted PWD response from an FTP server. When the client connects to a server and receives an overly long directory string in response to the PWD command, the client fails to properly validate the length of the input before copying it into a fixed-size buffer. This results in memory corruption and allows remote attackers to execute arbitrary code on the client system.
Security readout for executives and security teams
Plain-English summary
This flaw can let a malicious FTP server take control of a Windows system running an old Xftp client. The risk comes from the client trusting an overly long PWD directory response and corrupting memory. Treat any legacy Xftp 3.0 or earlier use as urgent to find and retire.
Executive priority
Prioritize this as a legacy software removal issue with critical impact. The vulnerable client is old, public exploit references exist, and compromise affects the endpoint running the client. Absence from KEV lowers evidence of active exploitation, not technical severity.
Technical view
Xftp FTP Client up to and including 3.0 build 0238 has a stack-based buffer overflow in handling PWD responses. A crafted, overly long directory string from an FTP server can corrupt memory and allow arbitrary code execution on the client system. The source bundle maps this to CWE-121 and CVSS 4.0 score 9.3.
Likely exposure
Exposure is most likely on endpoints or admin workstations still running legacy NetSarang Xftp 3.0 build 0238 or earlier. Risk requires the vulnerable client to connect to a malicious or compromised FTP server that returns the crafted PWD response.
Exploitation context
The bundle cites public exploit references in Metasploit and Exploit-DB, so proof-of-concept or exploit material exists publicly. KEV is false in the provided data, and no cited source states active exploitation in the wild.
Researcher notes
The CVSS vector lists UI:N, but the description says the client connects to a server and receives a malicious PWD response. Validate exposure around client-side FTP workflows, not server ownership alone. Vendor patch status is not established in the bundle, so avoid assuming a specific fixed version.
Mitigation direction
Identify and remove Xftp 3.0 build 0238 and earlier from endpoints.
Replace with a supported Xftp release or another maintained FTP client.
Check NetSarang guidance for vendor-approved fixes or upgrade paths.
Restrict legacy FTP client use to trusted destinations until removed.
Prioritize systems used by administrators or with privileged network access.
Validation and detection
Query endpoint software inventory for NetSarang Xftp installations and versions.
Confirm whether any detected install is version 3.0 build 0238 or earlier.
Review EDR telemetry for legacy Xftp execution on user and admin systems.
Check proxy, firewall, or DNS logs for FTP connections from affected endpoints.
Document compensating controls if removal cannot happen immediately.
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: yesTechnical 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.