radare2 up to 5.x null pointer dereference

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.
4.5$0-$5k0.00

Summaryinfo

A vulnerability has been found in radare2 up to 5.x and classified as problematic. The affected element is an unknown function. This manipulation causes null pointer dereference. This vulnerability is registered as CVE-2022-0419. The attack needs to be launched locally. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in radare2 up to 5.x (Programming Tool Software) and classified as problematic. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability.

The weakness was published 02/01/2022. It is possible to read the advisory at huntr.dev. This vulnerability is known as CVE-2022-0419 since 01/31/2022. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 6.0.0 eliminates this vulnerability. Applying the patch feaa4e7f7399c51ee6f52deb84dc3f795b4035d6 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.6
VulDB Meta Temp Score: 4.6

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.9
CNA Vector (huntr.dev): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: radare2 6.0.0
Patch: feaa4e7f7399c51ee6f52deb84dc3f795b4035d6

Timelineinfo

01/31/2022 🔍
02/01/2022 +1 days 🔍
02/01/2022 +0 days 🔍
02/04/2022 +3 days 🔍

Sourcesinfo

Advisory: feaa4e7f7399c51ee6f52deb84dc3f795b4035d6
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2022-0419 (🔍)
GCVE (CVE): GCVE-0-2022-0419
GCVE (VulDB): GCVE-100-192055

Entryinfo

Created: 02/01/2022 15:26
Updated: 02/04/2022 09:28
Changes: 02/01/2022 15:26 (50), 02/04/2022 09:28 (3)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!