In LibTIFF 4.0.8, there is a heap-based buffer overflow in the t2pwritepdf function in tools/tiff2pdf.c. This heap overflow could lead to different damages. For example, a crafted TIFF document can lead to an out-of-bounds read in TIFFCleanup, an invalid free in TIFFClose or t2pfree, memory corruption in t2preadwritepdfimage, or a double free in t2pfree. Given these possibilities, it probably could cause arbitrary code execution.

In LibTIFF 4.0.8, there is a memory leak in tifjbig.c. A crafted TIFF document can lead to a memory leak resulting in a remote denial of service attack.

Last updated 25 August 2025

In LibTIFF 4.0.8, there is a denial of service vulnerability in the TIFFOpen function. A crafted input will lead to a denial of service attack. During the TIFFOpen process, tdimagelength is not checked. The value of tdimagelength can be directly controlled by an input file. In the ChopUpSingleUncompressedStrip function, the TIFFCheckMalloc function is called based on tdimagelength. If we set the value of tdimagelength close to the amount of system memory, it will hang the system or trigger the OOM killer.

DISPUTED In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2pwriteproc function in tiff2pdf.c. NOTE: there is a third-party report of inability to reproduce this issue.

Last updated 24 July 2024

In LibTIFF 4.0.8, there is a assertion abort in the TIFFWriteDirectoryTagCheckedLong8Array function in tifdirwrite.c. A crafted input will lead to a remote denial of service attack.