Guest-triggered process crash via blit integer overflow
Published Apr 27, 2020 · Updated Aug 4, 2024
Integer overflow in QEMU 4.0.1 through 4.2.0 allows guest OS users to crash the QEMU process through crafted ATI VGA MMIO writes. The ati_2d_blt() routine lets programmed destination coordinates exceed their validated limits, causing address arithmetic to wrap before pixman_blt() performs an out-of-bounds memory access. Guest access to an emulated ATI VGA device is required, and exploitation interrupts the affected virtual machine by terminating its QEMU process.
Summary
What happened
Integer overflow in QEMU 4.0.1 through 4.2.0 allows guest OS users to crash the QEMU process through crafted ATI VGA MMIO writes. The ati_2d_blt() routine lets programmed destination coordinates exceed their validated limits, causing address arithmetic to wrap before pixman_blt() performs an out-of-bounds memory access. Guest access to an emulated ATI VGA device is required, and exploitation interrupts the affected virtual machine by terminating its QEMU process.
The record
- CVE
- CVE-2020-11869
- Published
- Apr 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 27, 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