Security readout for executives and security teams
Plain-English summary
WinSCP 5.17.8 can crash, and may have other unspecified impact, when it connects to a malicious FTP server that presents an overly long filename. Business risk is mainly endpoint disruption during file-transfer workflows. Public data does not provide CVSS, CPEs, or confirmed exploitation.
Executive priority
Treat this as a moderate endpoint risk unless WinSCP 5.17.8 is widely used with external FTP servers. Prioritize inventory first, then upgrade or restrict affected workflows based on confirmed business exposure.
Technical view
The CVE describes a buffer overflow in WinSCP 5.17.8 triggered by a long filename supplied by a malicious FTP server. The documented impact is denial of service, with possible unspecified additional impact. The source bundle does not identify a CWE, fixed version, exploit maturity, or affected CPE list.
Likely exposure
Likely exposure is Windows endpoints using WinSCP 5.17.8 to connect to attacker-controlled or compromised FTP servers. Exposure is lower where WinSCP is absent, FTP is unused, or connections are limited to trusted servers. The source data does not provide complete affected-product metadata.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not listed as KEV. Exploitation would require a malicious or compromised FTP server interacting with a vulnerable WinSCP client. Do not assume broader remote exposure from the available evidence.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, fixed version, or exploit status is provided in the bundle. The key technical condition is client-side handling of a long FTP filename from a malicious server. Avoid claiming code execution without vendor or CVE evidence.
Mitigation direction
- Identify endpoints running WinSCP 5.17.8.
- Check WinSCP tracker and vendor guidance for fixed versions or mitigations.
- Upgrade or remove vulnerable WinSCP installations where vendor guidance supports it.
- Restrict FTP use to trusted servers where operationally feasible.
- Monitor endpoint crashes involving WinSCP during FTP file listings.
Validation and detection
- Inventory installed WinSCP versions across managed endpoints.
- Confirm whether FTP connections are used in business workflows.
- Review WinSCP tracker item 1924 for vendor disposition.
- Check EDR or helpdesk logs for WinSCP crash patterns.
- Validate that upgraded endpoints no longer run version 5.17.8.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2020-28864 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://winscp.net/forum/viewtopic.php?t=30085CVE reference · x_refsource_MISC
- https://winscp.net/tracker/1924CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.