CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5). EPSS 1.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain CVE-2024-2002 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-2002?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-2002?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-2002 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| libdwarf_project:libdwarf | from 0.1.0 before 0.9.2 |
| redhat:enterprise_linux | 7.0 |
| redhat:enterprise_linux | 8.0 |
| fedoraproject:fedora | 40 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | dwarfutils | no fix listed | DEBIAN-CVE-2024-2002 |
| Debian | 13, 14 | dwarfutils | 1:0.11.1-1 | DEBIAN-CVE-2024-2002 |
| Ubuntu | 22.04:LTS, 24.04:LTS | dwarfutils | no fix listed | UBUNTU-CVE-2024-2002 |
| Azure Linux | 2 | libdwarf | 0.9.0-3 | AZL-35908 |
| Azure Linux | 3 | libdwarf | 0.9.2-1 | AZL-42087 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat rates this Moderate.
The double deallocation issue in libdwarf represents a moderate severity concern due to its potential to cause memory corruption and undefined behavior within the application. When memory is deallocated twice, it can lead to a range of unpredictable outcomes, including crashes, data corruption, and vulnerabilities that could be exploited maliciously. In a multi-threaded environment or in complex applications relying on libdwarf, such issues can be particularly challenging to diagnose and rectify. Additionally, the inconsistency in memory management can propagate errors across different parts of the software, complicating debugging efforts and potentially compromising the stability and security of the system..
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | libdwarf | Out of support scope | |
| Red Hat Enterprise Linux 8 | libdwarf | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-2002.