dbcve.org
LibtiffApplication

CVE-2017-7594

MEDIUM · 5.5 CVSS v3.0 Published 2017-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
The OJPEGReadHeaderInfoSecTablesDcTable function in tif_ojpeg.c in LibTIFF 4.0.7 allows remote attackers to cause a denial of service (memory leak) via a crafted image.

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 memory leak vulnerability in LibTIFF 4.0.7's OJPEG codec (tif_ojpeg.c, function OJPEGReadHeaderInfoSecTablesDcTable) allows remote attackers to cause a denial of service by providing specially crafted TIFF images that fail to properly free allocated memory during OJPEG header parsing.

MitigationUpgrade to a patched version of LibTIFF; implement input validation for TIFF files before processing to reject untrusted images.

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
LibtiffApplication
Affected:= 4.0.7

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 installed LibTIFF version
    Run 'tiffinfo -version' or check your package manager for libtiff version, or inspect the shared library file (e.g., libtiff.so.5 or libtiff.so.6)
    Affected if Version is exactly 4.0.7
  2. Confirm OJPEG codec is present
    Check if libtiff was compiled with OJPEG support - examine the binary or check for tif_ojpeg.c compilation
    Affected if OJPEG codec module exists in the installation
  3. Determine if your application/processes use OJPEG-compressed TIFF files
    Inspect your TIFF files using 'tiffinfo <file>' or 'tiff2pdf -i <file>' and look for 'Old-style JPEG' compression in the output
    Affected if TIFF files using Old-style JPEG (OJPEG) compression are processed
  4. Check for memory growth during TIFF processing
    Monitor memory usage of processes that handle TIFF files, particularly when processing multiple OJPEG-compressed images
    Affected if Memory usage continuously increases without being freed when processing OJPEG TIFF files

You are affected if you run LibTIFF version 4.0.7 and process TIFF files using Old-style JPEG (OJPEG) compression, as the memory leak occurs during OJPEG header parsing in those specific files.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of LibTIFF; implement input validation for TIFF files before processing to reject untrusted images.

Fix this in Libtiff Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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