Process crash via reentrant hook cleanup
Published May 27, 2022 · Updated Aug 3, 2024
Use-after-free in Unicorn Engine 1.0.3 allows local users to crash an embedding process through a reentrant hook callback. A memory-read-unmapped hook that calls emu_start recursively leaves deleted hook state for clear_deleted_hooks to dereference after its lifetime ends. The embedding application must invoke emulation from that callback, and triggering the path terminates the host process with a null-pointer fault.
Summary
What happened
Use-after-free in Unicorn Engine 1.0.3 allows local users to crash an embedding process through a reentrant hook callback. A memory-read-unmapped hook that calls emu_start recursively leaves deleted hook state for clear_deleted_hooks to dereference after its lifetime ends. The embedding application must invoke emulation from that callback, and triggering the path terminates the host process with a null-pointer fault.
The record
- CVE
- CVE-2022-29692
- Published
- May 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- local
- 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.
Weakness, pattern, technique
Public exploit references
- Null pointer caused by UAF in unicorn-1.0.3proof 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