Bug 1813322 (CVE-2020-10251) - CVE-2020-10251 ImageMagick: out-of-bounds read in ReadHEICImageByID function in coders/heic.c
Summary: CVE-2020-10251 ImageMagick: out-of-bounds read in ReadHEICImageByID function ...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2020-10251
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: 1813323 1813324
Blocks: 1813325
TreeView+ depends on / blocked
 
Reported: 2020-03-13 14:18 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-02-16 20:28 UTC (History)
4 users (show)

Fixed In Version: ImageMagick 7.0.10-0, ImageMagick 6.9.11-0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-24 16:32:06 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-03-13 14:18:51 UTC
In ImageMagick 7.0.9, an out-of-bounds read vulnerability exists within the ReadHEICImageByID function in coders\heic.c. It can be triggered via an image with a width or height value that exceeds the actual size of the image.

Reference:
https://github.com/ImageMagick/ImageMagick/issues/1859

Comment 1 Guilherme de Almeida Suckevicz 2020-03-13 14:19:10 UTC
Created ImageMagick tracking bugs for this issue:

Affects: epel-8 [bug 1813323]
Affects: fedora-all [bug 1813324]

Comment 3 Riccardo Schirone 2020-03-24 14:42:56 UTC
Support for HEIC images was added, according to the ChangeLogs, in upstream version 7.0.7-22 and 6.9.9-34.

Comment 4 Riccardo Schirone 2020-03-24 14:53:16 UTC
Statement:

This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they did not include support for HEIC images.

Comment 5 Product Security DevOps Team 2020-03-24 16:32:06 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-2020-10251


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