Guest-to-host code execution via unchecked UAS stream index
Published Aug 25, 2021 · Updated Aug 3, 2024
Out-of-bounds write in QEMU UAS emulation before 6.2.0-rc0 allows guest OS users to crash QEMU or execute code on the host. In hw/usb/dev-uas.c, the device uses a guest-supplied stream number without bounds checks when indexing UASDevice->data3 and UASDevice->status3. Exploitation requires control of a guest configured with the USB Attached SCSI device; memory corruption occurs in the host QEMU process.
Summary
What happened
Out-of-bounds write in QEMU UAS emulation before 6.2.0-rc0 allows guest OS users to crash QEMU or execute code on the host. In hw/usb/dev-uas.c, the device uses a guest-supplied stream number without bounds checks when indexing UASDevice->data3 and UASDevice->status3. Exploitation requires control of a guest configured with the USB Attached SCSI device; memory corruption occurs in the host QEMU process.
The record
- CVE
- CVE-2021-3713
- Published
- Aug 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 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=qemu 6.2.0-rc0
What conditions does exploitation require?
What is affected?
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