Process crash via mismatched Mach-O segment counts
Published Mar 24, 2022 · Updated Aug 2, 2024
Heap buffer overflow in radare2 before 5.6.6 allows local users to crash the process by analyzing a crafted Mach-O file. iterate_chained_fixups indexes chained_starts up to bin->nsegs even when the file-derived allocation contains fewer segment entries. Local analysis of attacker-supplied Mach-O input reaches the flaw, causing a heap out-of-bounds read that can terminate the process.
Summary
What happened
Heap buffer overflow in radare2 before 5.6.6 allows local users to crash the process by analyzing a crafted Mach-O file. iterate_chained_fixups indexes chained_starts up to bin->nsegs even when the file-derived allocation contains fewer segment entries. Local analysis of attacker-supplied Mach-O input reaches the flaw, causing a heap out-of-bounds read that can terminate the process.
The record
- CVE
- CVE-2022-1052
- Published
- Mar 24, 2022
- Updated
- Aug 2, 2024
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-787, CWE-122, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <5.6.6
What conditions does exploitation require?
What is affected?
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
- huntr.dev crashing reproducerproof 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