A null pointer dereference issue was found in Libtiff's tifdirinfo.c file. This issue may allow an attacker to trigger memory allocation failures through certain means, such as restricting the heap space size or just injecting faults, which would cause segmentation fault. This may cause an application crash, eventually leading to a denial of service.
References: https://gitlab.com/libtiff/libtiff/-/mergerequests/559 https://gitlab.com/libtiff/libtiff/-/issues/624
A flaw was found in the libtiff library. An out-of-memory issue in the TIFFReadEncodedStrip function can be triggered when processing a crafted tiff file, allowing attackers to perform memory allocation of arbitrary sizes, resulting in a denial of service.
Reference: https://gitlab.com/libtiff/libtiff/-/issues/620
Upstream patch: https://gitlab.com/libtiff/libtiff/-/mergerequests/553
A flaw was found in the libtiff library. An out-of-memory issue in the TIFFReadEncodedStrip function can be triggered when processing a crafted tiff file, allowing attackers to perform memory allocation of arbitrary sizes, resulting in a denial of service.
Reference: https://gitlab.com/libtiff/libtiff/-/issues/620
Upstream patch: https://gitlab.com/libtiff/libtiff/-/mergerequests/553
An issue was found in the tiffcp utility distributed by the libtiff package. Processing a crafted TIFF file may cause a heap-based buffer overflow, resulting in an application crash.
Reference: https://gitlab.com/libtiff/libtiff/-/issues/606
libtiff 4.5.0 is vulnerable to Buffer Overflow via /libtiff/tools/tiffcrop.c:8499. Incorrect updating of buffer size after rotateImage() in tiffcrop cause heap-buffer-overflow and SEGV.
https://gitlab.com/libtiff/libtiff/-/issues/520 https://gitlab.com/libtiff/libtiff/-/mergerequests/467
Last updated 24 July 2024
LibTIFF 4.4.0 has an out-of-bounds read in tiffcp in tools/tiffcp.c:948, 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/-/issues/277 https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-4645.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/e813112545942107551433d61afd16ac094ff246
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3609, 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 33aee127.
References: https://gitlab.com/libtiff/libtiff/-/issues/497 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0804.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3516, 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 33aee127.
References: https://gitlab.com/libtiff/libtiff/-/issues/501 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0803.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3724, 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 33aee127.
References: https://gitlab.com/libtiff/libtiff/-/issues/500 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0802.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in libtiff/tifunix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6778, 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 33aee127.
References: https://gitlab.com/libtiff/libtiff/-/issues/498 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0801.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
LibTIFF 4.4.0 has an out-of-bounds write in tiffcrop in tools/tiffcrop.c:3502, 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 33aee127.
References: https://gitlab.com/libtiff/libtiff/-/issues/496 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0800.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/33aee1275d9d1384791d2206776eb8152d397f00
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3701, 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 afaabc3e.
References: https://gitlab.com/libtiff/libtiff/-/issues/494 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0799.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3400, 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 afaabc3e.
References: https://gitlab.com/libtiff/libtiff/-/issues/492 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0798.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in libtiff/tifunix.c:368, invoked by tools/tiffcrop.c:2903 and tools/tiffcrop.c:6921, 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 afaabc3e.
References: https://gitlab.com/libtiff/libtiff/-/issues/495 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0797.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3592, 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 afaabc3e.
References: https://gitlab.com/libtiff/libtiff/-/issues/499 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0796.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
LibTIFF 4.4.0 has an out-of-bounds read in tiffcrop in tools/tiffcrop.c:3488, 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 afaabc3e.
References: https://gitlab.com/libtiff/libtiff/-/issues/493 https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0795.json
Upstream patch: https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68
processCropSelections in tools/tiffcrop.c in LibTIFF through 4.5.0 has a heap-based buffer overflow (e.g., "WRITE of size 307203") via a crafted TIFF image.
https://gitlab.com/libtiff/libtiff/-/issues/488 https://gitlab.com/libtiff/libtiff/-/commit/d1b6b9c1b3cae2d9e37754506c1ad8f4f7b646b5
Last updated 24 July 2024
It was found in libtiff 4.4.0rc1 that there is an invalid pointer free operation in TIFFClose() at tifclose.c:131 called by tiffcrop.c:2522 that can cause a program crash and denial of service while processing crafted input.
Upstream bug:
https://gitlab.com/libtiff/libtiff/-/issues/422
Upstream fix:
https://gitlab.com/libtiff/libtiff/-/mergerequests/378
It was found in libtiff 4.4.0rc1 that there is an invalid pointer free operation in TIFFClose() at tifclose.c:131 called by tiffcrop.c:2522 that can cause a program crash and denial of service while processing crafted input.
A flaw was found in libtiff 4.4.0rc1. There is a sysmalloc assertion fail in rotateImage() at tiffcrop.c:8621 that can cause program crash when reading a crafted input.
Upstream bug:
https://gitlab.com/libtiff/libtiff/-/issues/424
Upstream fix:
https://gitlab.com/libtiff/libtiff/-/mergerequests/378
A flaw was found in libtiff 4.4.0rc1. There is a sysmalloc assertion fail in rotateImage() at tiffcrop.c:8621 that can cause program crash when reading a crafted input.
There is a double free or corruption in rotateImage() at tiffcrop.c:8839 found in libtiff 4.4.0rc1
Upstream issue:
https://gitlab.com/libtiff/libtiff/-/issues/423
Upstream fix:
https://gitlab.com/libtiff/libtiff/-/mergerequests/378
There is a double free or corruption in rotateImage() at tiffcrop.c:8839 found in libtiff 4.4.0rc1
Divide By Zero error in tiffcrop in libtiff 4.4.0 allows 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 f3a5e010.
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2058.json https://gitlab.com/libtiff/libtiff/-/mergerequests/346 https://gitlab.com/libtiff/libtiff/-/issues/428
Accelerate Framework. A memory consumption issue was addressed with improved memory handling.
LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tiflzw.c:624, 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 b4e79bfa.
A stack-buffer-overflow flaw was found in tiffcp.c in main()
References: https://gitlab.com/libtiff/libtiff/-/issues/400 https://gitlab.com/libtiff/libtiff/-/mergerequests/323
A stack buffer overflow flaw was found in Libtiffs' tiffcp.c in main() function. This flaw allows an attacker to pass a crafted TIFF file to the tiffcp tool, triggering a stack buffer overflow issue, possibly corrupting the memory, and causing a crash that leads to a denial of service.