dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2024-2002

HIGH · 7.5 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 0.9.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A double-free vulnerability was found in libdwarf. In a multiply-corrupted DWARF object, libdwarf may try to dealloc(free) an allocation twice, potentially causing unpredictable and various results.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A double-free vulnerability exists in libdwarf, a library for parsing DWARF debug information. When processing a maliciously or accidentally corrupted DWARF object file, libdwarf may attempt to free the same memory allocation twice, leading to undefined behavior including potential code execution or denial of service.

MitigationUpdate libdwarf to the latest patched version. Additionally, validate and sanitize DWARF debug files from untrusted sources before processing them with libdwarf-based tools.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise LinuxOperating system
Affected:= 7.0= 8.0
FedoraOperating system
Affected:= 40
LibdwarfApplication
Affected:>= 0.1.0, < 0.9.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify libdwarf installation
    Run 'rpm -qa | grep libdwarf' on RHEL/Fedora, or check for libdwarf shared library via 'ldconfig -p | grep dwarf' and then retrieve version from the library file using 'objdump -p /path/to/libdwarf.so | grep version' or checking the package metadata
    Affected if libdwarf is installed and its version is unknown or matches the affected ranges
  2. Determine libdwarf version
    On RHEL/Fedora use 'rpm -q --queryformat '%{VERSION}' libdwarf'. On other systems, check the library file directly: 'strings /usr/lib*/libdwarf.so* | grep -E '^0\.[0-9]+\.[0-9]+$' | sort -V' or check pkg-config output 'pkg-config --modversion libdwarf'
    Affected if The installed version is less than 0.9.2 or falls within RHEL 7.0, 8.0 or Fedora 40 specific packages
  3. Identify tools using libdwarf
    Run 'ldd $(which dwarfdump 2>/dev/null) 2>/dev/null | grep dwarf' or 'ldd /usr/bin/*dwarf* 2>/dev/null | grep dwarf' to find binaries that link against libdwarf. Also check for applications that process DWARF debug information such as debuggers, disassemblers, or analysis tools
    Affected if Any tool that parses DWARF debug files is in use on the system
  4. Check for untrusted DWARF input processing
    Review system logs and audit traces for libdwarf-based tools processing debug files from network sources, user uploads, or third-party packages. Inspect any automated pipelines that consume debug information from external sources
    Affected if The system processes DWARF debug files from untrusted or potentially corrupted sources

A system is affected if libdwarf version 0.9.1 or earlier is installed AND any tool using libdwarf processes DWARF debug files, particularly from untrusted or corrupted sources

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.9.2 or later
Fixed in 0.9.2
Interim mitigation

Update libdwarf to the latest patched version. Additionally, validate and sanitize DWARF debug files from untrusted sources before processing them with libdwarf-based tools.

Recommended fix Moderate confidence

libdwarf 0.9.2 or later

  1. 1. Identify all applications and packages that depend on libdwarf in your environment
  2. 2. For Enterprise Linux systems: Run 'yum update libdwarf' or 'dnf update libdwarf' to apply the latest available package
  3. 3. For Fedora systems: Run 'dnf update libdwarf' to upgrade to the fixed version
  4. 4. For other distributions or direct compilation: Download libdwarf version 0.9.2 or later from the official source (github.com)
  5. 5. Rebuild any applications that were linked against the old libdwarf version
  6. 6. Restart any running services that use libdwarf-dependent applications
  7. 7. Verify the installed version using 'rpm -q libdwarf' or checking the library file directly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2002 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data