CVE-2017-9935: Buffer Overflow
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/tiffto a version that resolves this vulnerability.Fixed in 4.2.0-1+deb11u5Fixed in 4.2.0-1+deb11u8Fixed in 4.5.0-6+deb12u4Fixed in 4.7.0-3+deb13u2Fixed in 4.7.0-3+deb13u3Fixed in 4.7.2-1
Event History
Frequently Asked Questions
What is the severity of CVE-2017-9935?
CVE-2017-9935 is classified as a high-severity vulnerability due to the potential for a heap-based buffer overflow leading to memory corruption.
How do I fix CVE-2017-9935?
To remediate CVE-2017-9935, upgrade to a fixed version of LibTIFF, such as 4.2.0-1+deb11u5 or later.
Which versions of LibTIFF are affected by CVE-2017-9935?
CVE-2017-9935 affects LibTIFF versions up to and including 4.0.8.
What software packages are vulnerable to CVE-2017-9935?
Vulnerable packages related to CVE-2017-9935 include tiff on Debian systems and multiple versions of LibTIFF.
What could happen if I am affected by CVE-2017-9935?
If affected by CVE-2017-9935, a crafted TIFF document could lead to out-of-bounds reads or memory corruption, potentially resulting in application crashes or exploitation.