Process crash via malformed adf command
Published Aug 19, 2022 · Updated Aug 4, 2024
Null pointer dereference in radare2 before 4.4.0 allows local users to crash the process by issuing a malformed adf command. The anal_fcn_data function calls r_anal_function_size_from_entry on the null result of r_anal_get_fcn_in before checking whether a function exists. Local command access is required, and exploitation terminates only the affected radare2 process.
Summary
What happened
Null pointer dereference in radare2 before 4.4.0 allows local users to crash the process by issuing a malformed adf command. The anal_fcn_data function calls r_anal_function_size_from_entry on the null result of r_anal_get_fcn_in before checking whether a function exists. Local command access is required, and exploitation terminates only the affected radare2 process.
The record
- CVE
- CVE-2020-27795
- Published
- Aug 19, 2022
- Updated
- Aug 4, 2024
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-908, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in v4.4.0.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- adf command crash 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