Bug 2043722 (CVE-2021-44648)

Summary: CVE-2021-44648 gdk-pixbuf: heap-buffer overflow when decoding the lzw compressed stream of image data
Product: [Other] Security Response Reporter: Todd Cullum <tcullum>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: erik-fedora, eterrell, fedora, gnome-sig, klember, manisandro, mclasen, otte, rh-spice-bugs, rjones, virt-maint
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in gdk-pixbuf. The vulnerability occurs due to the index overwriting in the lzw_decoder_new function, leading to a heap buffer overflow. This flaw allows an attacker to input a specially crafted GIF file, leading to a crash or code execution.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 14:47:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 2044345, 2044346, 2046622, 2049411    
Bug Blocks: 2043718    

Description Todd Cullum 2022-01-21 20:25:11 UTC
GNOME gdk-pixbuf 2.42.6 is vulnerable to a heap-buffer overflow vulnerability
when decoding the lzw compressed stream of image data in GIF files with lzw
minimum code size equals to 12.


Comment 3 Sandipan Roy 2022-01-27 05:16:41 UTC
Created gdk-pixbuf2 tracking bugs for this issue:

Affects: fedora-all [bug 2046622]

Comment 4 Sandipan Roy 2022-02-02 07:36:05 UTC
Created mingw-gdk-pixbuf tracking bugs for this issue:

Affects: fedora-all [bug 2049411]

Comment 5 errata-xmlrpc 2023-05-09 07:18:04 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2023:2216 https://access.redhat.com/errata/RHSA-2023:2216

Comment 6 Product Security DevOps Team 2023-05-09 14:46:59 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):