radare2 2.7.0 Mini Crash Dump File mdmp.c r_bin_mdmp_init_directory_entry memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in radare2 2.7.0. It has been rated as critical. This affects the function r_bin_mdmp_init_directory_entry of the file mdmp.c of the component Mini Crash Dump File Handler. This manipulation causes memory corruption.
This vulnerability is tracked as CVE-2018-14016. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability has been found in radare2 2.7.0 (Programming Tool Software) and classified as critical. Affected by this vulnerability is the function r_bin_mdmp_init_directory_entry of the file mdmp.c of the component Mini Crash Dump File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The r_bin_mdmp_init_directory_entry function in mdmp.c in radare2 2.7.0 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted Mini Crash Dump file.
The bug was discovered 06/26/2018. The weakness was disclosed 07/12/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2018-14016 since 07/12/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 16 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-121388 and VDB-121386 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
06/26/2018 🔍07/12/2018 🔍
07/12/2018 🔍
07/12/2018 🔍
07/13/2018 🔍
04/09/2023 🔍
Sources
Advisory: eb7deb281df54771fb8ecf5890dc325a7d22d3e2Status: Not defined
CVE: CVE-2018-14016 (🔍)
GCVE (CVE): GCVE-0-2018-14016
GCVE (VulDB): GCVE-100-121387
See also: 🔍
Entry
Created: 07/13/2018 09:10Updated: 04/09/2023 07:31
Changes: 07/13/2018 09:10 (59), 03/04/2020 15:27 (1), 04/09/2023 07:31 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.