In LibTIFF 4.0.8, there is a heap-based buffer overflow in the t2p_write_pdf 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 t2p_free, memory corruption in t2p_readwrite_pdf_image, or a double free in t2p_free. Given these possibilities, it probably could cause arbitrary code execution.
The product reads data past the end, or before the beginning, of the intended buffer.
Link | Tags |
---|---|
https://usn.ubuntu.com/3606-1/ | third party advisory vendor advisory |
http://bugzilla.maptools.org/show_bug.cgi?id=2704 | issue tracking patch exploit third party advisory |
https://lists.debian.org/debian-lts-announce/2017/12/msg00008.html | third party advisory mailing list |
http://www.securityfocus.com/bid/99296 | vdb entry third party advisory |
https://www.debian.org/security/2018/dsa-4100 | third party advisory vendor advisory |