Host process crash via unchecked frame index
Published May 28, 2020 · Updated Aug 4, 2024
Out-of-bounds read in QEMU 5.0.0 and earlier allows guest OS users to crash the host QEMU process through MegaRAID emulation. megasas_lookup_frame converts a guest-controlled reply_queue_head value into a negative signed index and reads s->frames[] without adequate bounds checks. Exploitation requires control of a guest configured with the emulated MegaRAID SAS 8708EM2 controller; the reported consequence is a host QEMU process crash.
Summary
What happened
Out-of-bounds read in QEMU 5.0.0 and earlier allows guest OS users to crash the host QEMU process through MegaRAID emulation. megasas_lookup_frame converts a guest-controlled reply_queue_head value into a negative signed index and reads s->frames[] without adequate bounds checks. Exploitation requires control of a guest configured with the emulated MegaRAID SAS 8708EM2 controller; the reported consequence is a host QEMU process crash.
The record
- CVE
- CVE-2020-13362
- Published
- May 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 28, 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.
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