Application crash via null extraction-data dereference
Published Jul 22, 2022 · Updated Aug 3, 2024
NULL pointer dereference in radare2 5.7.2 allows local users to crash the application by opening a crafted binary file. In r_bin_file_xtr_load_buffer in libr/bin/bfile.c, failed LZ4 extraction leaves a null RBinXtrData pointer whose member is then written. Exploitation requires the crafted file to be opened with r2 and interrupts only that process in the current user's context.
Summary
What happened
NULL pointer dereference in radare2 5.7.2 allows local users to crash the application by opening a crafted binary file. In r_bin_file_xtr_load_buffer in libr/bin/bfile.c, failed LZ4 extraction leaves a null RBinXtrData pointer whose member is then written. Exploitation requires the crafted file to be opened with r2 and interrupts only that process in the current user's context.
The record
- CVE
- CVE-2022-34520
- Published
- Jul 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2022CVE publishedPublication date reported by the CVE source.
- Aug 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.
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
- Crafted 32-byte XALZ binary proof of conceptproof 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