| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in radareorg radare2 up to 5.7.x and classified as problematic. Impacted is an unknown function. Performing a manipulation results in integer overflow. This vulnerability was named CVE-2022-4398. The attack needs to be approached locally. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in radareorg radare2 up to 5.7.x (Programming Tool Software). This affects an unknown part. The manipulation with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Integer Overflow or Wraparound in GitHub repository radareorg/radare2 prior to 5.8.0.
The weakness was presented 12/10/2022. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2022-4398 since 12/10/2022. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 257973 (Linux Distros Unpatched Vulnerability : CVE-2022-4398), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.8.0 eliminates this vulnerability. Applying the patch b53a1583d05c3a5bfe5fa60da133fe59dfbb02b8 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.
The vulnerability is also documented in the vulnerability database at Tenable (257973). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 6.1
CNA Vector (huntr.dev): 🔍
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: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 257973
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-4398
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: radare2 5.8.0
Patch: b53a1583d05c3a5bfe5fa60da133fe59dfbb02b8
Timeline
12/10/2022 🔍12/10/2022 🔍
12/10/2022 🔍
08/29/2025 🔍
Sources
Product: github.comAdvisory: b53a1583d05c3a5bfe5fa60da133fe59dfbb02b8
Status: Confirmed
CVE: CVE-2022-4398 (🔍)
GCVE (CVE): GCVE-0-2022-4398
GCVE (VulDB): GCVE-100-215253
Entry
Created: 12/10/2022 22:24Updated: 08/29/2025 09:35
Changes: 12/10/2022 22:24 (51), 01/02/2023 12:41 (1), 01/02/2023 12:48 (11), 08/29/2025 09:35 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.