dbcve.org
Debian LinuxOperating system · Debian

CVE-2016-5322

MEDIUM · 5.5 CVSS v3.0 Published 2017-04-11
Fix available
A fix is available. Upgrade to after 4.0.6 or later.
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 setByteArray function in tif_dir.c in libtiff 4.0.6 and earlier allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted tiff 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

The setByteArray function in tif_dir.c in libtiff 4.0.6 and earlier contains an out-of-bounds read vulnerability. When processing a specially crafted TIFF image, the function fails to properly validate array bounds before reading data, allowing a remote attacker to trigger a denial of service via memory read beyond allocated buffers.

MitigationUpgrade libtiff to a version newer than 4.0.6 that includes the security patch for this vulnerability. Additionally, implement input validation and restrict processing of untrusted TIFF files until the upgrade can be completed.

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
Debian LinuxOperating system
Affected:= 8.0= 9.0
LibtiffApplication
Affected:<= 4.0.6

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. Detect if libtiff is installed
    Run 'dpkg -l | grep libtiff' on Debian/Ubuntu, or 'rpm -qa | grep libtiff' on Red Hat/CentOS, or check for the presence of libtiff library files in /usr/lib/
    Affected if libtiff packages or library files are found on the system
  2. Retrieve the installed libtiff version
    Run 'dpkg -l libtiff5' (Debian) or 'rpm -q libtiff' (Red Hat) to display the exact version number, or use 'tiffinfo -version' if the tools are installed
    Affected if a version number is returned showing libtiff is present
  3. Compare version against affected range
    Check if the installed version is 4.0.6 or earlier. For Debian, versions 8.0 and 9.0 are explicitly listed as affected. Compare your installed version number to 4.0.6
    Affected if the installed version is 4.0.6 or earlier, or the package version matches Debian 8.0 or 9.0

If libtiff is installed and the version is 4.0.6 or earlier (or Debian 8.0/9.0), the system is affected by this out-of-bounds read vulnerability in tif_dir.c.

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
Upgrade available Upgrade to a release after 4.0.6
Interim mitigation

Upgrade libtiff to a version newer than 4.0.6 that includes the security patch for this vulnerability. Additionally, implement input validation and restrict processing of untrusted TIFF files until the upgrade can be completed.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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