Process crash via malformed PYC object parsing
Published Feb 8, 2022 · Updated Aug 2, 2024
Use-after-free in radare2 before 5.6.2 allows attackers to crash the application by inducing parsing of a crafted PYC file. The get_array_object_generic error path frees previously parsed objects while the PYC reference table can still retain them, leaving dangling references. Exploitation requires an affected user or automated workflow to open or analyze the malicious file; the upstream reproducer demonstrates a process crash.
Summary
What happened
Use-after-free in radare2 before 5.6.2 allows attackers to crash the application by inducing parsing of a crafted PYC file. The get_array_object_generic error path frees previously parsed objects while the PYC reference table can still retain them, leaving dangling references. Exploitation requires an affected user or automated workflow to open or analyze the malicious file; the upstream reproducer demonstrates a process crash.
The record
- CVE
- CVE-2022-0523
- Published
- Feb 8, 2022
- Updated
- Aug 2, 2024
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- 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.2
What conditions does exploitation require?
What is affected?
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
- harep2.pyc 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