Bug 2142740 (CVE-2022-3599) - CVE-2022-3599 libtiff: out-of-bounds read in writeSingleSection in tools/tiffcrop.c
Summary: CVE-2022-3599 libtiff: out-of-bounds read in writeSingleSection in tools/tiff...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2022-3599
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2148888 2148889 2148890 2148891 2155752
Blocks: 2137106
TreeView+ depends on / blocked
 
Reported: 2022-11-15 06:34 UTC by Dhananjay Arunesh
Modified: 2026-06-29 18:29 UTC (History)
31 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-05-09 17:42:58 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:2340 0 None None None 2023-05-09 07:31:33 UTC

Description Dhananjay Arunesh 2022-11-15 06:34:44 UTC 
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
Comment 5 Dhananjay Arunesh 2022-11-28 09:37:34 UTC 
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 2148888]
Comment 8 errata-xmlrpc 2023-05-09 07:31:31 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2023:2340 https://access.redhat.com/errata/RHSA-2023:2340
Comment 9 Product Security DevOps Team 2023-05-09 17:42:55 UTC 
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-3599
Note You need to log in before you can comment on or make changes to this bug.