Process crash via unchecked relocation-map dereference
Published Dec 29, 2022 · Updated Apr 9, 2025
NULL pointer dereference in radare2 before 5.8.2 allows context-dependent attackers to crash the process via a crafted input file. The io.bank read paths call map->reloc_map->read for relocation-enabled maps without first verifying that reloc_map exists. A victim must open or analyze attacker-controlled content that creates this inconsistent map state; exploitation interrupts only the affected radare2 process.
Summary
What happened
NULL pointer dereference in radare2 before 5.8.2 allows context-dependent attackers to crash the process via a crafted input file. The io.bank read paths call map->reloc_map->read for relocation-enabled maps without first verifying that reloc_map exists. A victim must open or analyze attacker-controlled content that creates this inconsistent map state; exploitation interrupts only the affected radare2 process.
The record
- CVE
- CVE-2022-4843
- Published
- Dec 29, 2022
- Updated
- Apr 9, 2025
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 29, 2022CVE publishedPublication date reported by the CVE source.
- Apr 9, 2025Record 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.8.2
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
- POCbank 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