| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Radare2 up to 5.5.1/5.5.3/5.5.x/5.6.1. This issue affects some unknown processing. The manipulation leads to resource consumption. This vulnerability is traded as CVE-2021-4021. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Radare2 up to 5.5.1/5.5.3/5.5.x/5.6.1 (Programming Tool Software). It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability.
The weakness was shared 02/25/2022 as 19436. The advisory is shared at github.com. The identification of this vulnerability is CVE-2021-4021 since 11/25/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 5.5.2, 5.5.4, 5.6.0 or 5.6.2 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Radare2 5.5.2/5.5.4/5.6.0/5.6.2
Timeline
11/25/2021 🔍02/25/2022 🔍
02/25/2022 🔍
02/26/2022 🔍
Sources
Advisory: 19436Status: Confirmed
CVE: CVE-2021-4021 (🔍)
GCVE (CVE): GCVE-0-2021-4021
GCVE (VulDB): GCVE-100-193769
Entry
Created: 02/25/2022 11:49Updated: 02/26/2022 16:04
Changes: 02/25/2022 11:49 (39), 02/26/2022 16:04 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.