dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2024-7006

HIGH · 7.5 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to after 4.6.0 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 null pointer dereference flaw was found in Libtiff via `tif_dirinfo.c`. This issue may allow an attacker to trigger memory allocation failures through certain means, such as restricting the heap space size or injecting faults, causing a segmentation fault. This can cause an application crash, eventually leading to a denial of service.

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 null pointer dereference vulnerability exists in Libtiff's tif_dirinfo.c component. When memory allocation fails due to constrained heap space or injected faults, the code attempts to dereference a null pointer, causing a segmentation fault that leads to denial of service.

MitigationUpgrade to a patched version of Libtiff that includes proper null pointer validation in tif_dirinfo.c, or implement input validation to detect and reject malformed TIFF files before processing.

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:= 8.0= 9.0
Enterprise Linux For Arm 64Operating system
Affected:= 9.2
Enterprise Linux For Power Little Endian EusOperating system
Affected:= 9.2
Enterprise Linux Server AusOperating system
Affected:= 9.2
LibtiffApplication
Affected:>= 3.5.1, <= 4.6.0

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. Check if Libtiff is installed
    On Linux/Unix systems, run 'ldconfig -p | grep -i tiff' or check for library files in /usr/lib/ or /usr/lib64/ directories (e.g., libtiff.so, libtiff.so.5)
    Affected if No Libtiff library files are found on the system, meaning the library is not installed
  2. Determine the installed Libtiff version
    Run 'rpm -q libtiff' (RHEL) or check the library version with 'strings /usr/lib/libtiff.so.X 2>/dev/null | grep -i version' or use 'tiffinfo -version' if available
    Affected if The installed version cannot be determined or is not displayed
  3. Compare version against affected range
    Verify the installed version falls within >= 3.5.1 and <= 4.6.0. For RHEL, also check if version matches: RHEL 8.0, 9.0, 9.2 for ARM64, Power Little Endian, or Server Aus variants
    Affected if The installed version is within 3.5.1 to 4.6.0 inclusive, or matches the listed RHEL versions, indicating the vulnerable code is present
  4. Confirm the vulnerable component exists
    Check for the presence of tif_dirinfo.c in the Libtiff source or binary installation. Look for tif_dirinfo.o object file or the compiled library containing this component using 'nm libtiff.so | grep dirinfo' or 'strings libtiff.so | grep tif_dirinfo'
    Affected if The tif_dirinfo component is found in the installed Libtiff library, confirming the vulnerable code path exists

If Libtiff is installed and its version falls within 3.5.1 to 4.6.0 (or matches the specific RHEL versions listed), the system is affected by this null pointer dereference vulnerability.

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 a release after 4.6.0
Interim mitigation

Upgrade to a patched version of Libtiff that includes proper null pointer validation in tif_dirinfo.c, or implement input validation to detect and reject malformed TIFF files before processing.

Recommended fix Moderate confidence

libtiff version containing the CVE-2024-7006 fix (check RedHat errata RHSA or Debian security advisory DSA for exact version)

  1. Update the system package cache: sudo dnf check-update (RHEL) or sudo apt update (Debian)
  2. Install the updated Libtiff package: sudo dnf update libtiff (RHEL) or sudo apt install libtiff4 (Debian)
  3. Restart any services or applications that use Libtiff to ensure the patched library is loaded
  4. Verify the fix by checking the installed version: rpm -q libtiff or dpkg -l | grep libtiff
Caveat Minor - this is a security update; ensure applications using Libtiff are tested after update

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

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7006 — 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-7006 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