Host file disclosure via backslash path traversal
Published Jan 21, 2020 · Updated Aug 4, 2024
Path traversal in libslirp 4.1.0 and QEMU 4.2.0 allows remote attackers with TFTP access to read files outside the TFTP root on Windows. The tftp.c path validation fails to recognize backslashes as Windows path separators when checking a requested file for parent-directory components. Exploitation requires an enabled, reachable SLiRP TFTP server on a Windows host and exposes files accessible to the host process.
Summary
What happened
Path traversal in libslirp 4.1.0 and QEMU 4.2.0 allows remote attackers with TFTP access to read files outside the TFTP root on Windows. The tftp.c path validation fails to recognize backslashes as Windows path separators when checking a requested file for parent-directory components. Exploitation requires an enabled, reachable SLiRP TFTP server on a Windows host and exposes files accessible to the host process.
The record
- CVE
- CVE-2020-7211
- Published
- Jan 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo