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.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://gitlab.com/libtiff/libtiff/-/commit/afaabc3e50d4e5d80a94143f7e3c997e7e410f68 | patch |
| https://gitlab.com/libtiff/libtiff/-/issues/494 | issue tracking patch vendor advisory exploit |
| https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-0799.json | vdb entry |
| https://lists.debian.org/debian-lts-announce/2023/02/msg00026.html | mailing list |
| https://www.debian.org/security/2023/dsa-5361 | vendor advisory |
| https://security.netapp.com/advisory/ntap-20230316-0003/ | |
| https://security.gentoo.org/glsa/202305-31 | vendor advisory |