Bug 2084260 (CVE-2022-1623) - CVE-2022-1623 libtiff: out-of-bounds read in LZWDecode
Summary: CVE-2022-1623 libtiff: out-of-bounds read in LZWDecode
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2022-1623
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2084261 2084263 2084264 2084265 2084266 2084267
Blocks: 2084262
TreeView+ depends on / blocked
 
Reported: 2022-05-11 18:46 UTC by Anten Skrabec
Modified: 2022-05-31 14:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An out-of-bounds read vulnerability was found in Libtiff's LZWDecode() function in libtiff/tif_lzw.c. This flaw allows an attacker to perform a denial-of-service attack via a crafted tiff file, leading to the application crashing.
Clone Of:
Environment:
Last Closed: 2022-05-30 12:31:09 UTC

Attachments (Terms of Use)

Description Anten Skrabec 2022-05-11 18:46:31 UTC 
LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tif_lzw.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.

https://gitlab.com/libtiff/libtiff/-/commit/b4e79bfa0c7d2d08f6f1e7ec38143fc8cb11394a
https://gitlab.com/libtiff/libtiff/-/issues/410
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1623.json
Comment 1 Anten Skrabec 2022-05-11 18:46:45 UTC 
Created iv tracking bugs for this issue:

Affects: fedora-34 [bug 2084261]
Comment 2 Anten Skrabec 2022-05-11 18:48:16 UTC 
Created iv tracking bugs for this issue:

Affects: fedora-35 [bug 2084265]


Created libtiff tracking bugs for this issue:

Affects: fedora-34 [bug 2084263]
Affects: fedora-35 [bug 2084266]


Created mingw-libtiff tracking bugs for this issue:

Affects: fedora-34 [bug 2084264]
Affects: fedora-35 [bug 2084267]
Comment 4 Product Security DevOps Team 2022-05-30 12:31:07 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-1623
Note You need to log in before you can comment on or make changes to this bug.