Memory corruption via stale I/O-bank tree pointer
Published Feb 8, 2022 · Updated Aug 2, 2024
Use-after-free in radare2 before 5.6.0 allows context-dependent attackers to corrupt memory by supplying a crafted binary file. The r_io_bank_map_add_top loop ignores a failed r_crbtree_delete operation and continues traversing the I/O-bank red-black tree with a stale node reference. The crafted file must be opened or analyzed; public evidence establishes unsafe memory reuse but does not demonstrate a specific post-corruption outcome.
Summary
What happened
Use-after-free in radare2 before 5.6.0 allows context-dependent attackers to corrupt memory by supplying a crafted binary file. The r_io_bank_map_add_top loop ignores a failed r_crbtree_delete operation and continues traversing the I/O-bank red-black tree with a stale node reference. The crafted file must be opened or analyzed; public evidence establishes unsafe memory reuse but does not demonstrate a specific post-corruption outcome.
The record
- CVE
- CVE-2022-0139
- Published
- Feb 8, 2022
- Updated
- Aug 2, 2024
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-416, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 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.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.
Public exploit references
- havoc4 crafted-binary 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