Bug 2235521 (CVE-2021-29390) - CVE-2021-29390 libjpeg-turbo: heap-buffer-overflow vulnerability in decompress_smooth_data in jdcoefct.c
Summary: CVE-2021-29390 libjpeg-turbo: heap-buffer-overflow vulnerability in decompres...
Keywords:
Status: NEW
Alias: CVE-2021-29390
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2235522 2235523 2235524 2235525 2236152 2236153 2236154
Blocks: 2235520
TreeView+ depends on / blocked
 
Reported: 2023-08-28 22:29 UTC by Chess Hazlett
Modified: 2024-04-30 10:02 UTC (History)
11 users (show)

Fixed In Version: libjpeg-turbo 2.1.0
Doc Type: If docs needed, set a value
Doc Text:
A heap buffer over-read flaw was found in libjpeg-turbo. For certain types of smoothed jpeg images, the decompress_smooth_data() function may improperly enter a condition statement that leads to heap memory read of uninitialized data, which may cause an application crash or loss of confidentiality.
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:2295 0 None None None 2024-04-30 10:02:17 UTC

Description Chess Hazlett 2023-08-28 22:29:09 UTC
libjpeg-turbo version 2.0.90 is vulnerable to a heap-buffer-overflow vulnerability in decompress_smooth_data in jdcoefct.c.

https://bugzilla.redhat.com/show_bug.cgi?id=1943797

Comment 3 TEJ RATHI 2023-08-30 13:22:04 UTC
Created chromium tracking bugs for this issue:

Affects: epel-all [bug 2236152]


Created libjpeg-turbo tracking bugs for this issue:

Affects: fedora-all [bug 2236153]


Created mingw-libjpeg-turbo tracking bugs for this issue:

Affects: fedora-all [bug 2236154]

Comment 8 errata-xmlrpc 2024-04-30 10:02:15 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:2295 https://access.redhat.com/errata/RHSA-2024:2295


Note You need to log in before you can comment on or make changes to this bug.