Guest-triggered host memory corruption via undersized PCI buffer
Published Mar 10, 2020 · Updated Aug 5, 2024
A buffer overflow in QEMU's bochs-display device in 4.0.0 allows guest OS users to corrupt host memory through PCIe configuration writes. The device sets its PCIe capability only after the PCI configuration buffer is sized, so extended-space writes exceed the allocation. The guest must receive bochs-display on a PCIe bus; the grounded result is QEMU memory corruption and crash, while host escape was suspected but not demonstrated.
Summary
What happened
A buffer overflow in QEMU's bochs-display device in 4.0.0 allows guest OS users to corrupt host memory through PCIe configuration writes. The device sets its PCIe capability only after the PCI configuration buffer is sized, so extended-space writes exceed the allocation. The guest must receive bochs-display on a PCIe bus; the grounded result is QEMU memory corruption and crash, while host escape was suspected but not demonstrated.
The record
- CVE
- CVE-2019-15034
- Published
- Mar 10, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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