Process crash via stale register-name pointer
Published Apr 8, 2022 · Updated Aug 2, 2024
Use-after-free in radare2 before 5.6.8 allows local users to crash the process by analyzing a crafted binary with the aaef command. In r_core_anal_esil, aaef retains a register-name pointer across register-arena operations that can invalidate the referenced storage, then dereferences the stale pointer. A local user must supply a crafted binary and induce its analysis; successful exploitation interrupts only that radare2 process.
Summary
What happened
Use-after-free in radare2 before 5.6.8 allows local users to crash the process by analyzing a crafted binary with the aaef command. In r_core_anal_esil, aaef retains a register-name pointer across register-arena operations that can invalidate the referenced storage, then dereferences the stale pointer. A local user must supply a crafted binary and induce its analysis; successful exploitation interrupts only that radare2 process.
The record
- CVE
- CVE-2022-1284
- Published
- Apr 8, 2022
- Updated
- Aug 2, 2024
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 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.8
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.
Public exploit references
- Huntr aaef use-after-free 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