Host memory corruption via unchecked ROM addresses
Published Jun 4, 2020 · Updated Aug 4, 2024
Out-of-bounds write in QEMU 4.0 and 4.1.0 allows attackers to corrupt host memory via a crafted kernel image. When rom->addr is less than addr, address subtraction positions d before dest, and memcpy writes image bytes to that invalid destination. Reachability requires control of an image supplied through -kernel; the write crashes QEMU or, in the upstream worst case, injects code into its process.
Summary
What happened
Out-of-bounds write in QEMU 4.0 and 4.1.0 allows attackers to corrupt host memory via a crafted kernel image. When rom->addr is less than addr, address subtraction positions d before dest, and memcpy writes image bytes to that invalid destination. Reachability requires control of an image supplied through -kernel; the write crashes QEMU or, in the upstream worst case, injects code into its process.
The record
- CVE
- CVE-2020-13765
- Published
- Jun 4, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 4, 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