REDHAT-BUG-2142740: Medium severity LibTIFF libtiff vulnerability
LibTIFF 4.4.0 has an out-of-bounds read in writeSingleSection in tools/tiffcrop.c:7345, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit e8131125.
References: https://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246 https://gitlab.com/libtiff/libtiff/-/issues/398 https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3599.json
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch e813112545942107551433d61afd16ac094ff246
Event History
Frequently Asked Questions
What must an attacker be able to do to trigger the issue?
An attacker needs to supply a crafted TIFF file that is processed by the affected tiffcrop code path. The documented impact is denial of service through an out-of-bounds read.
Which environments are most exposed?
Deployments that use tiffcrop to process TIFF files from untrusted sources are the relevant exposure scenario. The provided information specifically identifies LibTIFF 4.4.0 and tools/tiffcrop.c.
What can source-built deployments do if a packaged update is unavailable?
Users compiling LibTIFF from source can apply commit e813112545942107551433d61afd16ac094ff246, which is identified as the available fix.