Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| artful | released | 4.0.8-5ubuntu0.1 |
| devel | not-affected | 4.0.9-4 |
| esm-infra-legacy/trusty | released | 4.0.3-7ubuntu0.9 |
| esm-infra/xenial | released | 4.0.6-1ubuntu0.4 |
| precise/esm | ignored | |
| trusty | released | 4.0.3-7ubuntu0.9 |
| trusty/esm | released | 4.0.3-7ubuntu0.9 |
| upstream | released | 4.0.9-2 |
| vivid/ubuntu-core | DNE | |
| xenial | released | 4.0.6-1ubuntu0.4 |
Показывать по
6.8 Medium
CVSS2
8.8 High
CVSS3
Связанные уязвимости
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.
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.
In LibTIFF 4.0.8, there is a heap-based buffer overflow in the t2p_wri ...
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.
6.8 Medium
CVSS2
8.8 High
CVSS3