Bug 1491345 – CVE-2017-14325 ImageMagick: Memory leak in the PersistPixelCache function

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1491345 - (CVE-2017-14325) CVE-2017-14325 ImageMagick: Memory leak in the PersistPixelCache function

Summary:	CVE-2017-14325 ImageMagick: Memory leak in the PersistPixelCache function

Status:	NEW

Aliases:	CVE-2017-14325

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20170908,reported=2...
Keywords:	Security

Depends On:	1488981
Blocks:
	Show dependency tree / graph

Reported:	2017-09-13 10:21 EDT by Andrej Nemec
Modified:	2017-09-13 10:23 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrej Nemec 2017-09-13 10:21:49 EDT

In ImageMagick 7.0.7-1 Q16, a memory leak vulnerability was found in the function PersistPixelCache in magick/cache.c, which allows attackers to cause a denial of service (memory consumption in ReadMPCImage in coders/mpc.c) via a crafted file.

Upstream issue:

https://github.com/ImageMagick/ImageMagick/issues/741

Upstream patches:

https://github.com/ImageMagick/ImageMagick/commit/44a55580ac8c01d8cff1e6e0063820af113f8591
https://github.com/ImageMagick/ImageMagick/commit/7de19606bc006d2013b0b56cfe182f5e4fe510e2

Comment 1 Andrej Nemec 2017-09-13 10:23:51 EDT

Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1488981]

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