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 1350461 - (CVE-2016-5842) CVE-2016-5842 ImageMagick: Information leak in MagickCore/property.c
CVE-2016-5842 ImageMagick: Information leak in MagickCore/property.c
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20160622,reported=2...
: Security
Depends On: 1350462
Blocks: 1350463
  Show dependency treegraph
 
Reported: 2016-06-27 09:59 EDT by Adam Mariš
Modified: 2016-08-18 06:06 EDT (History)
13 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2016-06-27 09:59:48 EDT
An information leak vulnerability was found in MagickCore/property.c by partially controlling the pointer for reading arbitrary data from the memory of ImageMagick process.

Upstream patch:

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

CVE request:

http://seclists.org/oss-sec/2016/q2/586
Comment 1 Adam Mariš 2016-06-27 10:00:55 EDT
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1350462]
Comment 2 Stefan Cornelius 2016-08-18 06:06:29 EDT
Although we do have affected code snippets, I could not find an attack vector to exploit this prior to the following commit:
https://github.com/ImageMagick/ImageMagick/commit/e9438e2a82d35b6657e908ff38ec0303f432b655

Statement:

This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7.

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