CVE-2019-17320
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNetSarang XFTP Client 6.0149 and earlier version contains a buffer overflow vulnerability caused by improper boundary checks when copying file name from an attacker controlled FTP server. That leads attacker to execute arbitrary code by sending a crafted filename.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNetSarang XFTP Client versions 6.0149 and earlier contain a buffer overflow vulnerability due to improper boundary checks when copying filenames received from an FTP server. An attacker controlling a malicious FTP server can send a specially crafted filename that overflows a buffer, leading to arbitrary code execution on the client machine.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 6.0149CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate NetSarang XFTP Client installationCheck your system for installed programs named XFTP or NetSarang XFTP. Common locations include C:\Program Files\NetSarang or C:\Program Files (x86)\NetSarang in Windows, or look in your system's installed applications list.Affected if NetSarang XFTP Client is installed on the system
-
Determine the installed version numberRight-click the XFTP executable (typically xftp.exe) and select Properties, then view the Details tab to find the Product Version. Alternatively, open XFTP and navigate to Help > About to view the version information.Affected if The version displayed is 6.0149 or earlier
-
Compare version to affected rangeCompare your identified version against the affected range: any version less than or equal to 6.0149 is vulnerable. Versions later than 6.0149 are not affected by this CVE.Affected if The installed version is 6.0149 or any earlier version number
-
Assess FTP usage exposureDetermine if the XFTP Client is used to connect to external or untrusted FTP servers. This vulnerability is triggered only when receiving a specially crafted filename from a connected FTP server.Affected if The client connects to FTP servers and version is within the affected range
A user is affected if NetSarang XFTP Client version 6.0149 or earlier is installed AND the client is used to connect to FTP servers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate NetSarang XFTP Client to a version later than 6.0149. Until patched, avoid connecting to untrusted or unknown FTP servers.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17320 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data