Bug 1483111 – CVE-2017-12642 ImageMagick: Memory leak in ReadMPCImage function in coders/mpc.c$

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

Bug 1483111 - (CVE-2017-12642) CVE-2017-12642 ImageMagick: Memory leak in ReadMPCImage function in coders/mpc.c$

Summary:	CVE-2017-12642 ImageMagick: Memory leak in ReadMPCImage function in coders/mp...

Status:	NEW

Aliases:	CVE-2017-12642

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=20170808,reported=2...
Keywords:	Security

Depends On:	1483117
Blocks:
	Show dependency tree / graph

Reported:	2017-08-18 14:34 EDT by Pedro Sampaio
Modified:	2018-06-29 18:26 EDT (History)
CC List:	6 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 Pedro Sampaio 2017-08-18 14:34:57 EDT

ImageMagick 7.0.6-1 has a memory leak vulnerability in ReadMPCImage in coders\mpc.c.

Upstream bug:

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

Upstream patch:

https://github.com/ImageMagick/ImageMagick/commit/562d584a31fe5883cd0a93741026263fd0e8a232
https://github.com/ImageMagick/ImageMagick/commit/184a047627aa564b7062d2462aef668155caa390

References:

https://bugzilla.novell.com/show_bug.cgi?id=1052771

Comment 1 Pedro Sampaio 2017-08-18 14:55:47 EDT

Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1483117]

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