GNU Binutils 2.39 binutils/dwarf.c display_debug_names assertion

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in GNU Binutils 2.39. This issue affects the function display_debug_names of the file binutils/dwarf.c. The manipulation leads to assertion.
This vulnerability is documented as CVE-2022-38126. There is not any exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in GNU Binutils 2.39 (Programming Tool Software) and classified as problematic. This issue affects the function display_debug_names of the file binutils/dwarf.c. The manipulation with an unknown input leads to a assertion vulnerability. Using CWE to declare the problem leads to CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. Impacted is availability. The summary by CVE is:
Assertion fail in the display_debug_names() function in binutils/dwarf.c may lead to program crash and denial of service.
The weakness was released 09/02/2022. The advisory is shared at sourceware.org. The identification of this vulnerability is CVE-2022-38126 since 08/10/2022. Technical details are known, but no exploit is available.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at sourceware.org.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.gnu.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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: 🔍
Exploiting
Class: AssertionCWE: CWE-617
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: sourceware.org
Timeline
08/10/2022 🔍09/02/2022 🔍
09/02/2022 🔍
10/11/2022 🔍
Sources
Vendor: gnu.orgAdvisory: sourceware.org
Status: Confirmed
CVE: CVE-2022-38126 (🔍)
GCVE (CVE): GCVE-0-2022-38126
GCVE (VulDB): GCVE-100-207761
Entry
Created: 09/02/2022 09:50Updated: 10/11/2022 12:14
Changes: 09/02/2022 09:50 (42), 10/11/2022 12:14 (11)
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.