Bug 2124173 (CVE-2021-20224) - CVE-2021-20224 ImageMagick: integer overflow in ExportIndexQuantum() in MagickCore/quantum-export.c
Summary: CVE-2021-20224 ImageMagick: integer overflow in ExportIndexQuantum() in Magic...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2021-20224
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:
Blocks: 2122658
TreeView+ depends on / blocked
 
Reported: 2022-09-05 06:30 UTC by TEJ RATHI
Modified: 2022-11-25 06:28 UTC (History)
10 users (show)

Fixed In Version: ImageMagick 7.0.10-57, ImageMagick6 6.9.11-57
Doc Type: If docs needed, set a value
Doc Text:
An integer overflow issue was found in ImageMagick's ExportIndexQuantum() function in MagickCore/quantum-export.c. Function calls to GetPixelIndex() could result in outside the range of representable values for the type 'unsigned char.' When ImageMagick processes a crafted pdf file, this issue could lead to undefined behavior or a crash.
Clone Of:
Environment:
Last Closed: 2022-11-25 06:28:16 UTC


Attachments (Terms of Use)

Description TEJ RATHI 2022-09-05 06:30:28 UTC
An integer overflow issue was discovered in ImageMagick's ExportIndexQuantum() function in MagickCore/quantum-export.c. Function calls to GetPixelIndex() could result in values outside the range of representable for the 'unsigned char'. When ImageMagick processes a crafted pdf file, this could lead to an undefined behaviour or a crash.

https://github.com/ImageMagick/ImageMagick/commit/5af1dffa4b6ab984b5f13d1e91c95760d75f12a6
https://github.com/ImageMagick/ImageMagick/pull/3083
https://github.com/ImageMagick/ImageMagick6/commit/553054c1cb1e4e05ec86237afef76a32cd7c464d

Comment 2 Product Security DevOps Team 2022-11-25 06:28:15 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-2021-20224


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