Bug 1513940 – CVE-2017-16546 ImageMagick: Invalid memory allocation in the ReadWPGImage 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 1513940 - (CVE-2017-16546) CVE-2017-16546 ImageMagick: Invalid memory allocation in the ReadWPGImage function

Summary:	CVE-2017-16546 ImageMagick: Invalid memory allocation in the ReadWPGImage fun...

Status:	CLOSED WONTFIX

Aliases:	CVE-2017-16546

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

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-11-16 05:29 EST by Andrej Nemec
Modified:	2017-11-16 05:30 EST (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:	2017-11-16 05:30:35 EST
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-11-16 05:29:28 EST

The ReadWPGImage function in coders/wpg.c in ImageMagick 7.0.7-9 does not properly validate the colormap index in a WPG palette, which allows attackers to cause a denial of service (use of uninitialized data or invalid memory allocation).

Upstream issue:

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

Upstream patch:

https://github.com/ImageMagick/ImageMagick/commit/e04cf3e9524f50ca336253513d977224e083b816

Comment 1 Andrej Nemec 2017-11-16 05:30:41 EST

Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

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