Host process crash via unchecked vmxnet3 parameters
Published Feb 25, 2021 · Updated Aug 3, 2024
Integer overflow in QEMU 5.2.0 and earlier allows guest OS users to crash the host QEMU process through crafted vmxnet3 parameters. vmxnet3_activate_device() passes guest-controlled MTU and transmit, completion, and receive ring sizes into device setup without enforcing defined bounds. Exploitation requires high privileges in a guest configured with the vmxnet3 adapter, and the bounded consequence is interruption of that QEMU instance.
Summary
What happened
Integer overflow in QEMU 5.2.0 and earlier allows guest OS users to crash the host QEMU process through crafted vmxnet3 parameters. vmxnet3_activate_device() passes guest-controlled MTU and transmit, completion, and receive ring sizes into device setup without enforcing defined bounds. Exploitation requires high privileges in a guest configured with the vmxnet3 adapter, and the bounded consequence is interruption of that QEMU instance.
The record
- CVE
- CVE-2021-20203
- Published
- Feb 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-190, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=versions up to v5.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.
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