dbcve.org
OpensuseOperating system

CVE-2016-5321

MEDIUM · 6.5 CVSS v3.0 Published 2017-01-20
Fix available
A fix is available. Upgrade to after 4.0.6 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 DumpModeDecode function in libtiff 4.0.6 and earlier allows attackers to cause a denial of service (invalid read and crash) 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

A denial of service vulnerability exists in libtiff 4.0.6 and earlier in the DumpModeDecode function. Attackers can trigger an invalid memory read by providing a specially crafted TIFF image, causing the application to crash.

MitigationUpgrade to libtiff version 4.0.7 or later where the vulnerability has been patched. As a defense-in-depth measure, validate and sanitize untrusted 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
OpensuseOperating system
Affected:= 13.1
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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/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. Check if libtiff is installed
    Use the system's package manager to query for libtiff. On RPM-based systems (e.g., SUSE, RHEL), run `rpm -qa | grep -i libtiff`. On Debian-based systems, run `dpkg -l | grep -i libtiff`. Alternatively, check for the library file (e.g., `ls /usr/lib/libtiff.so*`).
    Affected if libtiff package or library file is present on the system.
  2. Determine the installed version of libtiff
    On RPM-based systems (including SUSE), run `rpm -q --queryformat "%{VERSION}" libtiff`. On Debian-based systems, run `dpkg -s libtiff | grep Version`. If the library file exists, you can also inspect its version with `objdump -p /usr/lib/libtiff.so.X | grep VERSION` (replace X with the actual version number from the library filename).
    Affected if version is 4.0.6 or earlier.
  3. Verify the version is within the affected range
    Compare the version obtained in the previous step to 4.0.6. If the version number is less than or equal to 4.0.6 (e.g., 4.0.5, 4.0.4, etc.), the installation is vulnerable.
    Affected if version <= 4.0.6.

The system is affected if libtiff version 4.0.6 or earlier is installed and the system processes TIFF images (especially untrusted ones).

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 to libtiff version 4.0.7 or later where the vulnerability has been patched. As a defense-in-depth measure, validate and sanitize untrusted TIFF files before processing.

Fix this in Opensuse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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