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 t2p_free. Given these possibilities, it probably could cause arbitrary code execution.
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "libtiff-doc": "4.0.3-7ubuntu0.9", "libtiff5-dbgsym": "4.0.3-7ubuntu0.9", "libtiff-opengl": "4.0.3-7ubuntu0.9", "libtiffxx5-dbgsym": "4.0.3-7ubuntu0.9", "libtiff4-dev": "4.0.3-7ubuntu0.9", "libtiff-opengl-dbgsym": "4.0.3-7ubuntu0.9", "libtiff-tools-dbgsym": "4.0.3-7ubuntu0.9", "libtiff5": "4.0.3-7ubuntu0.9", "libtiff5-alt-dev": "4.0.3-7ubuntu0.9", "libtiff-tools": "4.0.3-7ubuntu0.9", "libtiffxx5": "4.0.3-7ubuntu0.9", "libtiff5-dev": "4.0.3-7ubuntu0.9" } ] }
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "libtiff-doc": "4.0.6-1ubuntu0.4", "libtiff5-dbgsym": "4.0.6-1ubuntu0.4", "libtiff-opengl": "4.0.6-1ubuntu0.4", "libtiffxx5-dbgsym": "4.0.6-1ubuntu0.4", "libtiff-opengl-dbgsym": "4.0.6-1ubuntu0.4", "libtiff-tools-dbgsym": "4.0.6-1ubuntu0.4", "libtiff5": "4.0.6-1ubuntu0.4", "libtiff-tools": "4.0.6-1ubuntu0.4", "libtiffxx5": "4.0.6-1ubuntu0.4", "libtiff5-dev": "4.0.6-1ubuntu0.4" } ] }