Bug 1894232 (CVE-2020-27755)

Summary:	CVE-2020-27755 ImageMagick: memory leaks in ResizeMagickMemory function in ImageMagick/MagickCore/memory.c
Product:	[Other] Security Response	Reporter:	Guilherme de Almeida Suckevicz <gsuckevi>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	fedora, jhorak, mike, pahan, rhel8-maint, security-response-team, stransky
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	ImageMagick 7.0.9-0	Doc Type:	If docs needed, set a value
Doc Text:	in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the proper image depth size does not reset the size in the event there is an invalid size. The patch resets the depth to a proper size before throwing an exception. The memory leak can be triggered by a crafted input file that is processed by ImageMagick and could cause an impact to application reliability, such as denial of service.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-24 23:34:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1901253, 1901254, 1910551
Bug Blocks:	1891602

Description Guilherme de Almeida Suckevicz 2020-11-03 19:03:33 UTC

In ImageMagick, there are memory leaks detected in ResizeMagickMemory at MagickCore/memory.c.

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

Upstream patch:
https://github.com/ImageMagick/ImageMagick/commit/f28e9e56e1b56d4e1f09d2a56d70892ae295d6a4

Comment 1 Guilherme de Almeida Suckevicz 2020-11-03 19:03:35 UTC

Acknowledgments:

Name: Suhwan Song (Seoul National University)

Comment 2 Todd Cullum 2020-11-03 23:19:18 UTC

Flaw summary:

in SetImageExtent() of /MagickCore/image.c, an incorrect image depth size can cause a memory leak because the code which checks for the proper image depth size does not reset the size in the event there is an invalid size. The patch resets the depth to a proper size before throwing an exception. The memory leak can be triggered by a crafted input file that is processed by ImageMagick and could cause an impact to application reliability, such as denial of service.

Comment 3 Todd Cullum 2020-11-03 23:21:21 UTC

Statement:

This flaw is out of support scope for Red Hat Enterprise Linux 5, 6, and 7. Inkscape is not affected because it no longer uses a bundled ImageMagick in Red Hat Enterprise Linux 8. For more information regarding support scopes, please see https://access.redhat.com/support/policy/updates/errata .

Comment 4 Guilherme de Almeida Suckevicz 2020-11-24 19:17:10 UTC

Created ImageMagick tracking bugs for this issue:

Affects: epel-8 [bug 1901253]
Affects: fedora-all [bug 1901254]

Comment 5 Product Security DevOps Team 2020-11-24 23:34:32 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-27755