Process crash via null NE OS pointer
Published Nov 14, 2025 · Updated Nov 14, 2025
NULL pointer dereference in radare2 6.0.5 and earlier allows local users to crash the process by opening a crafted NE binary. The bin_ne.c info() function passes a null ne->os pointer to strdup during malformed NE parsing, causing strlen to read address zero. Exploitation requires a user or automated analysis pipeline to open the file, and the bounded consequence is termination of that radare2 process.
Summary
What happened
NULL pointer dereference in radare2 6.0.5 and earlier allows local users to crash the process by opening a crafted NE binary. The bin_ne.c info() function passes a null ne->os pointer to strdup during malformed NE parsing, causing strlen to read address zero. Exploitation requires a user or automated analysis pipeline to open the file, and the bounded consequence is termination of that radare2 process.
The record
- CVE
- CVE-2025-63745
- Published
- Nov 14, 2025
- Updated
- Nov 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 14, 2025CVE publishedPublication date reported by the CVE source.
- Nov 14, 2025Record 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.
Weakness, pattern, technique
Public exploit references
- crash_002 malformed NE 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