radare 2.0.1 Size Validation elf.c store_versioninfo_gnu_verdef memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in radare 2.0.1. It has been rated as critical. The impacted element is the function store_versioninfo_gnu_verdef of the file libr/bin/format/elf/elf.c of the component Size Validation. Performing a manipulation results in memory corruption.
This vulnerability is known as CVE-2017-16357. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability, which was classified as critical, was found in radare 2.0.1. This affects the function store_versioninfo_gnu_verdef of the file libr/bin/format/elf/elf.c of the component Size Validation. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In radare 2.0.1, a memory corruption vulnerability exists in store_versioninfo_gnu_verdef() and store_versioninfo_gnu_verneed() in libr/bin/format/elf/elf.c, as demonstrated by an invalid free. This error is due to improper sh_size validation when allocating memory.
The bug was discovered 11/01/2017. The weakness was published 11/01/2017 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-16357 since 11/01/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-108887 and VDB-108886. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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
11/01/2017 🔍11/01/2017 🔍
11/01/2017 🔍
11/01/2017 🔍
11/02/2017 🔍
01/05/2023 🔍
Sources
Advisory: 0b973e28166636e0ff1fad80baa0385c9c09c53aStatus: Not defined
Confirmation: 🔍
CVE: CVE-2017-16357 (🔍)
GCVE (CVE): GCVE-0-2017-16357
GCVE (VulDB): GCVE-100-108885
See also: 🔍
Entry
Created: 11/02/2017 08:07Updated: 01/05/2023 14:26
Changes: 11/02/2017 08:07 (57), 12/02/2019 16:56 (2), 01/05/2023 14:26 (5)
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.