Process crash via unchecked binary symbol pointer
Published May 25, 2022 · Updated Aug 4, 2024
NULL pointer dereference in radare2 5.5.2 allows context-dependent attackers to crash the process through a crafted binary file. The symbols() parser treats an attacker-controlled empty element->symbols entry as a valid symbol and dereferences sym->paddr without a null check. Exploitation requires radare2 to process the file and interrupts only that process; no code execution or data exposure is reported.
Summary
What happened
NULL pointer dereference in radare2 5.5.2 allows context-dependent attackers to crash the process through a crafted binary file. The symbols() parser treats an attacker-controlled empty element->symbols entry as a valid symbol and dereferences sym->paddr without a null check. Exploitation requires radare2 to process the file and interrupts only that process; no code execution or data exposure is reported.
The record
- CVE
- CVE-2021-44974
- Published
- May 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- Issue 19478 crash-file 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