Skip to content
Fencer Intel
high 7.8

CVE-2016-10270 json

LibTIFF 4.0.7 allows remote attackers to cause a denial of service (heap-based buffer over-read) or possibly have unspecified other impact…

published 2017-03-24 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-1455

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

Summary

LibTIFF 4.0.7 allows remote attackers to cause a denial of service (heap-based buffer over-read) or possibly have unspecified other impact via a crafted TIFF image, related to "READ of size 8" and libtiff/tif_read.c:523:22.

Patch / fix

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

debian advisories DEBIAN-CVE-2016-10270

  • tiff SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 3.8.2-141.169.6.1
  • tiff SLES for SAP 12 SP2, SLES for SAP 12 SP1, SLES for Raspberry Pi 12 SP2 +6 more 4.0.7-43.1

suse advisories SUSE-SU-2018:1472-1SUSE-SU-2017:1044-1

  • tiff openSUSE Tumbleweed 4.3.0-1.3

opensuse advisories openSUSE-SU-2024:11461-1

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-10270 updated cvss 3.3

libtiff: Heap-based buffer overflow in tiff_read.c

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

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

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

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/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.