Host service interruption via file-descriptor exhaustion
Published May 4, 2020 · Updated Aug 4, 2024
Resource exhaustion in QEMU 5.0 virtiofsd allows guest OS users to interrupt host services by opening files in a shared directory. At startup, virtiofsd sets RLIMIT_NOFILE to 1,000,000 without capping it below the Linux host's fs.file-max limit, so a FUSE client can exhaust file descriptors system-wide. The attack requires a guest with a virtio-fs shared directory on a Linux host, and the resulting exhaustion can disrupt unrelated host processes.
Summary
What happened
Resource exhaustion in QEMU 5.0 virtiofsd allows guest OS users to interrupt host services by opening files in a shared directory. At startup, virtiofsd sets RLIMIT_NOFILE to 1,000,000 without capping it below the Linux host's fs.file-max limit, so a FUSE client can exhaust file descriptors system-wide. The attack requires a guest with a virtio-fs shared directory on a Linux host, and the resulting exhaustion can disrupt unrelated host processes.
The record
- CVE
- CVE-2020-10717
- Published
- May 4, 2020
- Updated
- Aug 4, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-770, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= QEMU v5.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