Service interruption via incomplete initialization cleanup
Published May 27, 2022 · Updated Aug 3, 2024
Memory leak in Unicorn Engine 2.0.0-rc7 allows context-dependent attackers to exhaust process memory through invalid CPU configuration. The uc_ctl API accepts an unsupported CPU model or mode, then uc_close frees only the engine object when initialization remains incomplete, leaving internal allocations such as l1_map unreleased. Reachability requires an embedding application to let attacker-controlled CPU settings reach the API repeatedly; the documented result is progressive memory consumption and eventual service interruption.
Summary
What happened
Memory leak in Unicorn Engine 2.0.0-rc7 allows context-dependent attackers to exhaust process memory through invalid CPU configuration. The uc_ctl API accepts an unsupported CPU model or mode, then uc_close frees only the engine object when initialization remains incomplete, leaving internal allocations such as l1_map unreleased. Reachability requires an embedding application to let attacker-controlled CPU settings reach the API repeatedly; the documented result is progressive memory consumption and eventual service interruption.
The record
- CVE
- CVE-2022-29695
- Published
- May 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665, T1499.004
- 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.
Weakness, pattern, technique
Public exploit references
- Invalid CPU mode memory-leak 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