Guest-triggered process crash via unchecked MMIO access sizes
Published Jun 2, 2020 · Updated Aug 4, 2024
Out-of-bounds access in QEMU 4.2.0 allows guest OS users to crash the host QEMU process through a crafted MSI-X MMIO address. memory_region_access_valid() ignored declared minimum and maximum access sizes when a device lacked an accepts callback, allowing invalid MSI-X MMIO accesses to reach hw/pci/msix.c. Control of a guest capable of issuing the malformed MMIO operation is required, and the bounded consequence is interruption of that virtual machine’s QEMU process.
Summary
What happened
Out-of-bounds access in QEMU 4.2.0 allows guest OS users to crash the host QEMU process through a crafted MSI-X MMIO address. memory_region_access_valid() ignored declared minimum and maximum access sizes when a device lacked an accepts callback, allowing invalid MSI-X MMIO accesses to reach hw/pci/msix.c. Control of a guest capable of issuing the malformed MMIO operation is required, and the bounded consequence is interruption of that virtual machine’s QEMU process.
The record
- CVE
- CVE-2020-13754
- Published
- Jun 2, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 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