Bug 1946739 (CVE-2021-20311) - CVE-2021-20311 ImageMagick: Division by zero in sRGBTransformImage() in MagickCore/colorspace.c
Summary: CVE-2021-20311 ImageMagick: Division by zero in sRGBTransformImage() in Magic...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2021-20311
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: 1946740 1946741 1947266
Blocks: 1946747 1946749
TreeView+ depends on / blocked
 
Reported: 2021-04-06 18:43 UTC by Pedro Sampaio
Modified: 2021-11-02 23:28 UTC (History)
4 users (show)

Fixed In Version: ImageMagick 7.0.11
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in ImageMagick, where a division by zero in sRGBTransformImage() in the MagickCore/colorspace.c may trigger undefined behavior via a crafted image file that is submitted by an attacker processed by an application using ImageMagick. The highest threat from this vulnerability is to system availability.
Clone Of:
Environment:
Last Closed: 2021-11-02 23:28:12 UTC
Embargoed:


Attachments (Terms of Use)

Description Pedro Sampaio 2021-04-06 18:43:07 UTC
A flaw was found in ImageMagick before version 7.0.11. A division by zero in sRGBTransformImage() in MagickCore/colorspace.c may trigger undefined behavior via crafted image file.

Upstream patch:

https://github.com/ImageMagick/ImageMagick/commit/70aa86f5d5d8aa605a918ed51f7574f433a18482

Comment 1 Pedro Sampaio 2021-04-06 18:43:37 UTC
Created ImageMagick tracking bugs for this issue:

Affects: epel-8 [bug 1946740]
Affects: fedora-all [bug 1946741]

Comment 2 Todd Cullum 2021-04-06 21:20:35 UTC
Statement:

This flaw is out of support scope for Red Hat Enterprise Linux 6 and 7. It does not affect Red Hat Enterprise Linux 8 because the ImageMagick package is not shipped. To learn more about Red Hat Enterprise Linux support scope, please see https://access.redhat.com/support/policy/updates/errata/ .


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