LibTIFF 4.3.0 has an out-of-bounds read in _TIFFmemcpy in tif_unix.c in certain situations involving a custom tag and 0x0200 as the second word of the DE field. Reference: https://gitlab.com/libtiff/libtiff/-/issues/355 Upstream patch: https://gitlab.com/libtiff/libtiff/-/merge_requests/287
Created libtiff tracking bugs for this issue: Affects: fedora-all [bug 2042604] Created mingw-libtiff tracking bugs for this issue: Affects: fedora-all [bug 2042605]
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2022:7585 https://access.redhat.com/errata/RHSA-2022:7585
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:8194 https://access.redhat.com/errata/RHSA-2022:8194
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-22844