CVE-2025-5643
Last modified
CVE-2025-5643 is a low-severity vulnerability rated 2.5/10 on the CVSS scale. A vulnerability classified as problematic was found in Radare2 5.9.9. Affected by this vulnerability is the function cons_stack_load in the library /libr/cons/cons.c of the component radiff2. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
A vulnerability classified as problematic was found in Radare2 5.9.9. Affected by this vulnerability is the function cons_stack_load in the library /libr/cons/cons.c of the component radiff2. The manipulation of the argument -T leads to memory corruption. An attack has to be approached locally. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The patch is named 5705d99cc1f23f36f9a84aab26d1724010b97798. It is recommended to apply a patch to fix this issue. The documentation explains that the parameter -T is experimental and "crashy". Further analysis has shown "the race is not a real problem unless you use asan". A new warning has been added.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Radare | Radare2 | 5.9.9 |
References
- https://github.com/radareorg/radare2/issues/24232Exploit, Issue Tracking, Vendor Advisory
- https://github.com/radareorg/radare2/issues/24232#issuecomment-2918841776Issue Tracking, Vendor Advisory
- https://vuldb.com/?ctiid.311131Permissions Required, VDB Entry
- https://vuldb.com/?id.311131Third Party Advisory, VDB Entry
- https://vuldb.com/?submit.586912Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-5643?
How severe is CVE-2025-5643?
How do I fix CVE-2025-5643?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-56423An issue in Austrian Academy of Sciences (AW) Austrian Archa…5.3
- CVE-2025-56424An issue in Insiders Technologies GmbH e-invoice pro before …7.5
- CVE-2025-56425An issue was discovered in the AppConnector component versio…9.1
- CVE-2025-56426An issue WebKul Bagisto v.2.3.6 allows a remote attacker to …6.5
- CVE-2025-56427Directory Traversal vulnerability in ComposioHQ v.0.7.20 all…7.5
- CVE-2025-56429Cross Site Scripting vulnerability in Fearless Geek Media Fe…6.1
- CVE-2025-56430Directory Traversal vulnerability in Fearless Geek Media Fea…7.5
- CVE-2025-56431Directory Traversal vulnerability in Fearless Geek Media Fea…7.5
- CVE-2025-56432A cross-site scripting (XSS) vulnerability exists in Nagios …6.1
- CVE-2025-56435SQL Injection vulnerability in FoxCMS v1.2.6 and before allo…5.3
- CVE-2025-56438An issue in the firmware update mechanism of Nous W3 Smart W…6.8
- CVE-2025-5644A vulnerability, which was classified as problematic, has be…2.5
Are you affected by CVE-2025-5643?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
