Libtiff vulnerabilitiesNone on the known-exploited list.

Vendor
The short answer

Libtiff has 256 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Libtiff, with 256. If you run Libtiff software, patch the exploited flaws first.

See the exploited flaws

We keep watching the known-exploited list.

Products

Which Libtiff products have the most vulnerabilities?

Libtiff leads with 256 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Libtiff256
Published vulnerabilities
Known exploited

Which Libtiff vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Libtiff's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Libtiff flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 54%

    Multiple stack-based buffer overflows in the TIFF library (libtiff) before 3.8.2, as used in Adobe Reader 9.3.0 and other products, allow context-dependent attackers to execute arbitrary code or cause a denial of...

    CVSS7.5Published3 Aug 2006
  2. 25%

    Heap-based buffer overflow in the cpSeparateBufToContigBuf function in tiffcp.c in LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0beta7, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4,...

    CVSS8.8Published26 Jun 2018
  3. 15%

    Integer overflow in (1) tif_dirread.c and (2) tif_fax3.c for libtiff 3.5.7 and 3.7.0 allows remote attackers to execute arbitrary code via a TIFF file containing a TIFF_ASCII or TIFF_UNDEFINED directory entry with a...

    CVSS10.0Published10 Jan 2005
  4. 15%

    LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0beta7, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.4beta, 4.0.5, 4.0.6, 4.0.7, 4.0.8 and 4.0.9 (with JBIG enabled) decodes...

    CVSS8.8Published22 Oct 2018
  5. 14%

    Stack-based buffer overflow in the tiffsplit command in libtiff 3.8.2 and earlier might might allow attackers to execute arbitrary code via a long filename.

    CVSS7.5Published30 May 2006
  6. 14%

    Stack-based buffer overflow in libTIFF before 3.7.2 allows remote attackers to execute arbitrary code via a TIFF file with a malformed BitsPerSample tag.

    CVSS7.5Published14 May 2005
  7. 14%

    Heap-based buffer overflow in the PackBitsPreEncode function in tif_packbits.c in bmp2tiff in libtiff 4.0.6 and earlier allows remote attackers to execute arbitrary code or cause a denial of service via a large width...

    CVSS9.8Published8 Jan 2016
  8. 14%

    ppm2tiff does not check the return value of the TIFFScanlineSize function, which allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted PPM image that triggers...

    CVSS6.8Published11 Nov 2012
  9. 11%

    Heap-based buffer overflow in tif_ojpeg.c in the OJPEG decoder in LibTIFF before 3.9.5 allows remote attackers to execute arbitrary code via a crafted TIFF file.

    CVSS6.8Published3 May 2011
  10. 11%

    Integer overflow in the TIFFFetchData function in tif_dirread.c for libtiff before 3.8.1 allows context-dependent attackers to cause a denial of service and possibly execute arbitrary code via a crafted TIFF image.

    CVSS6.5Published25 Apr 2006
Every product

All Libtiff products we track.

1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

Precursor Intelligence

Running Libtiff? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 256 published vulnerabilities across 1 product and 49 versions from Libtiff.

None of Libtiff's vulnerabilities is on the list of flaws known to be exploited today.

Libtiff, with 256 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Libtiff products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.