Radare2 5.9.9 radiff2 /libr/cons/cons.c r_cons_is_breaked -T memory corruption ⚔ [Disputed]

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.4$0-$5k0.00

Summaryinfo

A vulnerability was found in Radare2 5.9.9. It has been rated as problematic. Impacted is the function r_cons_is_breaked in the library /libr/cons/cons.c of the component radiff2. The manipulation of the argument -T leads to memory corruption. This vulnerability is traded as CVE-2025-5641. An attack has to be approached locally. Furthermore, there is an exploit available. It is still unclear if this vulnerability genuinely exists. It is suggested to install a patch to address 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". An additional warning regarding threading support has been added.

Detailsinfo

A vulnerability was found in Radare2 5.9.9. It has been rated as problematic. This issue affects the function r_cons_is_breaked in the library /libr/cons/cons.c of the component radiff2. The manipulation of the argument -T with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-5641. The exploitation is known to be difficult. An attack has to be approached locally. Technical details as well as a public exploit are known.

The exploit is available at drive.google.com. It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment. 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". An additional warning regarding threading support has been added.

Applying the patch 5705d99cc1f23f36f9a84aab26d1724010b97798 is able to eliminate this problem. The bugfix is ready for download at github.com.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-16973). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍

CVSSv3info

VulDB Meta Base Score: 2.5
VulDB Meta Temp Score: 2.4

VulDB Base Score: 2.5
VulDB Temp Score: 2.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 2.5
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: 5705d99cc1f23f36f9a84aab26d1724010b97798

Timelineinfo

06/04/2025 🔍
06/04/2025 +0 days 🔍
06/23/2025 +19 days 🔍

Sourcesinfo

Advisory: 24230
Status: Confirmed
Confirmation: 🔍
Disputed: 🔍

CVE: CVE-2025-5641 (🔍)
GCVE (CVE): GCVE-0-2025-5641
GCVE (VulDB): GCVE-100-311129
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 06/04/2025 14:05
Updated: 06/23/2025 16:56
Changes: 06/04/2025 14:05 (66), 06/04/2025 14:10 (6), 06/05/2025 11:37 (1), 06/23/2025 16:56 (31)
Complete: 🔍
Submitter: rootsec
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #586909: radare2 radiff2 5.9.9 and master branch Memory corruption (by rootsec)

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!