Process crash via freed pyc parser reference
Published Feb 8, 2022 · Updated Aug 2, 2024
Use-after-free in the radare2 pyc parser before 5.6.2 allows context-dependent attackers to crash the process via a crafted pyc file. The TYPE_UNKNOWN branch in get_object pops the current entry from the refs list immediately before freeing ret, leaving parser state referencing freed memory. Exploitation requires a user to open or analyze crafted Python bytecode; the publicly demonstrated consequence is a process crash.
Summary
What happened
Use-after-free in the radare2 pyc parser before 5.6.2 allows context-dependent attackers to crash the process via a crafted pyc file. The TYPE_UNKNOWN branch in get_object pops the current entry from the refs list immediately before freeing ret, leaving parser state referencing freed memory. Exploitation requires a user to open or analyze crafted Python bytecode; the publicly demonstrated consequence is a process crash.
The record
- CVE
- CVE-2022-0520
- 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
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