Process crash via PYC parser double free
Published May 14, 2021 · Updated Aug 3, 2024
Double free in the PYC parser in radareorg radare2 5.3.0 and earlier allows local users to crash the process via a crafted file. In extract_sections_symbols, error paths free objects that remain owned by shared lists, so later processing reads or frees the same allocation again. Exploitation requires analysis of attacker-supplied Python bytecode, and the demonstrated consequence is termination of the affected radare2 or rabin2 process.
Summary
What happened
Double free in the PYC parser in radareorg radare2 5.3.0 and earlier allows local users to crash the process via a crafted file. In extract_sections_symbols, error paths free objects that remain owned by shared lists, so later processing reads or frees the same allocation again. Exploitation requires analysis of attacker-supplied Python bytecode, and the demonstrated consequence is termination of the affected radare2 or rabin2 process.
The record
- CVE
- CVE-2021-32613
- Published
- May 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-416, CWE-415, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=radare2 versions before and including 5.3.0
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
- Upstream crafted-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