Bug 1348172 – CVE-2016-5691 ImageMagick: Possible out-of-bounds write in ReadDCMImage()

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1348172 - (CVE-2016-5691) CVE-2016-5691 ImageMagick: Possible out-of-bounds write in ReadDCMImage()

Summary:	CVE-2016-5691 ImageMagick: Possible out-of-bounds write in ReadDCMImage()

Status:	NEW

Aliases:	CVE-2016-5691

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

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

URL:
Whiteboard:	impact=moderate,public=20160614,repor...
Keywords:	Security

Depends On:	1348173
Blocks:	1348175
	Show dependency tree / graph

Reported:	2016-06-20 06:36 EDT by Adam Mariš
Modified:	2018-06-29 18:12 EDT (History)
CC List:	13 users (show)

See Also:
Fixed In Version:	ImageMagick 7.0.1-7, ImageMagick 6.9.4-5
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 Adam Mariš 2016-06-20 06:36:03 EDT

Possible out-of-bounds write in ReadDCMImage() function due to lack of validation of pixel.red, pixel.green, and pixel.blue.

Upstream fix:

https://github.com/ImageMagick/ImageMagick/commit/5511ef530576ed18fd636baa3bb4eda3d667665d

External References:

https://blog.fuzzing-project.org/46-Various-invalid-memory-reads-in-ImageMagick-WPG,-DDS,-DCM.html

CVE assignment:

http://seclists.org/oss-sec/2016/q2/564

Comment 1 Adam Mariš 2016-06-20 06:37:37 EDT

Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1348173]

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