Embedding process crash via failed host allocation
Published May 27, 2022 · Updated Aug 3, 2024
NULL pointer dereference in Unicorn Engine 2.0.0-rc7 and earlier allows context-dependent attackers to crash an embedding process. An oversized uc_mem_map request can exhaust host virtual memory while guest allocation state persists, causing qemu_ram_free to remove a NULL RAMBlock during uc_close. Reachability requires control over the mapping size supplied to the library, and the demonstrated consequence is an abort of the embedding process.
Summary
What happened
NULL pointer dereference in Unicorn Engine 2.0.0-rc7 and earlier allows context-dependent attackers to crash an embedding process. An oversized uc_mem_map request can exhaust host virtual memory while guest allocation state persists, causing qemu_ram_free to remove a NULL RAMBlock during uc_close. Reachability requires control over the mapping size supplied to the library, and the demonstrated consequence is an abort of the embedding process.
The record
- CVE
- CVE-2022-29694
- Published
- May 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- Oversized uc_mem_map crash proof of conceptproof of concept · demonstrated
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