Guest-to-host escape via unchecked special-file opens
Published Jan 28, 2021 · Updated Aug 4, 2024
Improper privilege management in QEMU Project QEMU 5.2.0 virtiofsd allows privileged guest OS users to access host devices through virtio-fs. FUSE_OPEN and related paths open device nodes without first checking the inode type, so a malicious guest driver makes the daemon operate on host special files. Exploitation requires a privileged guest OS user, a modified guest device driver, and a virtio-fs share; the resulting host-file read and write access breaches guest isolation.
Summary
What happened
Improper privilege management in QEMU Project QEMU 5.2.0 virtiofsd allows privileged guest OS users to access host devices through virtio-fs. FUSE_OPEN and related paths open device nodes without first checking the inode type, so a malicious guest driver makes the daemon operate on host special files. Exploitation requires a privileged guest OS user, a modified guest device driver, and a virtio-fs share; the resulting host-file read and write access breaches guest isolation.
The record
- CVE
- CVE-2020-35517
- Published
- Jan 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 28, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=qemu 5.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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