Memory exhaustion via unreleased invalid engine allocations
Published May 27, 2022 · Updated Aug 3, 2024
Memory leak in Unicorn Engine 2.0.0-rc7 and earlier allows attackers to consume process memory via an unsupported architecture value. The uc_open function allocates an engine object before validating its architecture, then returns UC_ERR_ARCH without freeing that object when init_arch remains unset. The condition requires consuming code to pass an invalid architecture identifier; repeated calls can exhaust memory, while closing the invalid handle can crash the process.
Summary
What happened
Memory leak in Unicorn Engine 2.0.0-rc7 and earlier allows attackers to consume process memory via an unsupported architecture value. The uc_open function allocates an engine object before validating its architecture, then returns UC_ERR_ARCH without freeing that object when init_arch remains unset. The condition requires consuming code to pass an invalid architecture identifier; repeated calls can exhaust memory, while closing the invalid handle can crash the process.
The record
- CVE
- CVE-2022-29693
- Published
- May 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, 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-architecture uc_open 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