dbcve.org
LibtiffApplication

CVE-2017-7593

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
tif_read.c in LibTIFF 4.0.7 does not ensure that tif_rawdata is properly initialized, which might allow remote attackers to obtain sensitive information from process memory 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 · high confidence

In LibTIFF 4.0.7, the tif_read.c component fails to properly initialize the tif_rawdata buffer before use. When processing a crafted TIFF image, this uninitialized memory region can be read and leaked, potentially exposing sensitive data from the process memory to an attacker.

MitigationUpdate to a patched version of LibTIFF that properly initializes tif_rawdata before reading image data, or rebuild LibTIFF with the fix applied.

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
High
Integrity
None
Availability
None

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

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 installed LibTIFF library version
    Run 'tiffinfo -version' or check the library file with 'pkg-config --modversion libtiff-4' or examine /usr/lib/libtiff.so* for version info
    Affected if The version reported is exactly 4.0.7
  2. Verify TIFF processing is in use
    Identify applications or services that process TIFF images (e.g., image converters, document management systems, CUPS print spooler) by checking running processes or examining application dependencies with 'ldd <executable>' or 'pkg-config --libs libtiff-4'
    Affected if The system runs any application that links against libtiff and processes TIFF files
  3. Confirm the vulnerable code path exists
    Check if libtiff is built from source version 4.0.7 by examining the library binary or source at tif_read.c for the uninitialized tif_rawdata buffer issue
    Affected if The library binary or source code matches the unpatched 4.0.7 release containing the initialization bug in tif_read.c

The environment is affected only if LibTIFF version 4.0.7 is installed AND it is being used to process TIFF images, as the vulnerability requires both the vulnerable library version and the TIFF processing code path to be exercised.

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

Update to a patched version of LibTIFF that properly initializes tif_rawdata before reading image data, or rebuild LibTIFF with the fix applied.

Fix this in Libtiff Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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