LibtiffApplication

CVE-2017-7592

HIGH · 7.8 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 →
81/100
Remediation priority · High
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 putagreytile function in tif_getimage.c in LibTIFF 4.0.7 has a left-shift undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact 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

A left-shift undefined behavior vulnerability exists in the putagreytile function in tif_getimage.c of LibTIFF 4.0.7. When processing specially crafted TIFF images, the code performs bit shifts that trigger undefined behavior according to C standards, potentially causing memory corruption leading to application crashes or other undefined behavior.

MitigationUpgrade to a patched version of LibTIFF (4.0.8 or later) that corrects the left-shift operation in the putagreytile function. Ensure all systems processing untrusted TIFF images are updated.

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

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 the library file version using 'strings libtiff.so | grep -i version' or check your package manager for the installed tiff package version
    Affected if The version is exactly 4.0.7
  2. Verify TIFF processing is available
    Check if any application or tool capable of processing TIFF images is installed - look for tiff2pdf, tiffinfo, or other TIFF utilities, or confirm libtiff is linked to any application
    Affected if LibTIFF 4.0.7 is present AND any TIFF processing capability exists on the system
  3. Confirm the vulnerable code path exists
    The vulnerability is in the putagreytile function within tif_getimage.c - any use of this function to decode greyscale TIFF images would trigger the left-shift undefined behavior
    Affected if Code using the putagreytile function processes specially crafted TIFF images

If the installed LibTIFF version is exactly 4.0.7 and any application processes TIFF images, the environment is affected by CVE-2017-7592

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 (4.0.8 or later) that corrects the left-shift operation in the putagreytile function. Ensure all systems processing untrusted TIFF images are updated.

Fix this in Libtiff Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-7592 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