Analyzer crash via unchecked null symbol type
Published Aug 22, 2023 · Updated Oct 3, 2024
A null-pointer dereference in radare2 5.4.0 and 5.4.2 allows attackers to crash the analyzer by supplying a corrupted ELF file. During ELF analysis, __core_anal_fcn passes sym->type to strcmp without first checking whether that symbol-type pointer is null. The flaw is reached when radare2 analyzes a corrupted ELF; exploitation interrupts that analysis process without reported data disclosure or modification.
Summary
What happened
A null-pointer dereference in radare2 5.4.0 and 5.4.2 allows attackers to crash the analyzer by supplying a corrupted ELF file. During ELF analysis, __core_anal_fcn passes sym->type to strcmp without first checking whether that symbol-type pointer is null. The flaw is reached when radare2 analyzes a corrupted ELF; exploitation interrupts that analysis process without reported data disclosure or modification.
The record
- CVE
- CVE-2022-28070
- Published
- Aug 22, 2023
- Updated
- Oct 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 3, 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
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