Local crash via unchecked symbol pointer
Published Feb 22, 2022 · Updated Aug 2, 2024
NULL pointer dereference in radare2 before 5.6.4 allows local users to crash the tool by opening a crafted binary file. In libr/bin/p/bin_symbols.c, the symbols() routine dereferences a symbol pointer without checking for null, and the upstream fix adds a guard before accessing sym->paddr. Exploitation requires local execution and user interaction to make radare2 process attacker-controlled binary data, resulting in a denial of service through process crash.
Summary
What happened
NULL pointer dereference in radare2 before 5.6.4 allows local users to crash the tool by opening a crafted binary file. In libr/bin/p/bin_symbols.c, the symbols() routine dereferences a symbol pointer without checking for null, and the upstream fix adds a guard before accessing sym->paddr. Exploitation requires local execution and user interaction to make radare2 process attacker-controlled binary data, resulting in a denial of service through process crash.
The record
- CVE
- CVE-2022-0712
- Published
- Feb 22, 2022
- Updated
- Aug 2, 2024
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-476, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 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.4
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
No public exploit references are available in this record.
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