Bug 2100044 (CVE-2021-46822) - CVE-2021-46822 libjpeg-turbo: heap buffer overflow in get_word_rgb_row() in rdppm.c
Summary: CVE-2021-46822 libjpeg-turbo: heap buffer overflow in get_word_rgb_row() in r...
Keywords:
Status: NEW
Alias: CVE-2021-46822
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: 2101764 2102187 2103011 2101702 2101704 2103010
Blocks: 2099351
TreeView+ depends on / blocked
 
Reported: 2022-06-22 09:07 UTC by TEJ RATHI
Modified: 2022-07-26 11:39 UTC (History)
27 users (show)

Fixed In Version: libjpeg-turbo 2.1.0
Doc Type: If docs needed, set a value
Doc Text:
A heap-based buffer overflow vulnerability was found in libjpeg-turbo in the get_word_rgb_row() function in rdppm.c. The flaw occurs when the PPM reader in libjpeg-turbo mishandles use of the tjLoadImage() function for loading a 16-bit binary PPM file into a grayscale uncompressed image buffer and then loading a 16-bit binary PGM file into an RGB uncompressed image buffer. This flaw allows a remote attacker to persuade a victim to open a specially-crafted file, causing the application to crash.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description TEJ RATHI 2022-06-22 09:07:30 UTC
The PPM reader in libjpeg-turbo through 2.0.90 mishandles use of tjLoadImage for loading a 16-bit binary PPM file into a grayscale buffer and loading a 16-bit binary PGM file into an RGB buffer. This is related to a heap-based buffer overflow in the get_word_rgb_row function in rdppm.c.

https://exchange.xforce.ibmcloud.com/vulnerabilities/221567
https://github.com/libjpeg-turbo/libjpeg-turbo/commit/f35fd27ec641c42d6b115bfa595e483ec58188d2

Comment 1 TEJ RATHI 2022-06-28 07:54:25 UTC
Created libjpeg-turbo tracking bugs for this issue:

Affects: fedora-all [bug 2101702]


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

Affects: fedora-all [bug 2101704]


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