Skip to content
Fencer Intel
medium 5.5

CVE-2016-5322 json

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 rea…

published 2017-04-11 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6273

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

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.

Patch / fix

  • tiff Debian 14, Debian 13, Debian 12 4.0.7-1

debian advisories DEBIAN-CVE-2016-5322

  • tiff Ubuntu 14.04 LTS 4.0.3-7ubuntu0.6
  • tiff Ubuntu 16.04 LTS 4.0.6-1ubuntu0.1

ubuntu advisories UBUNTU-CVE-2016-5322

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libtiff Arch Linux 4.0.7-1
  • lib32-libtiff Arch Linux 4.0.7-1

arch linux advisories AVG-85AVG-86

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-5322 updated cvss 4.3

libtiff: Out-of-bounds read in extractContigSamplesBytes() function

  • Red Hat Enterprise Linux 5 libtiff
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 libtiff Red Hat Enterprise Linux 7 libtiff, libtiff-tools, compat-libtiff3
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.