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 1354500 - (CVE-2016-5010) CVE-2016-5010 ImageMagick: Out-of-bounds read when processing crafted tiff file
CVE-2016-5010 ImageMagick: Out-of-bounds read when processing crafted tiff file
Status: CLOSED WONTFIX
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=20160714,reported=2...
: Security
Depends On: 1361578
Blocks: 1354508 1378785
  Show dependency treegraph
 
Reported: 2016-07-11 08:36 EDT by Adam Mariš
Modified: 2018-04-03 19:56 EDT (History)
11 users (show)

See Also:
Fixed In Version: ImageMagick 6.9.5-3
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-03 19:56:28 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-07-11 08:36:34 EDT
An out-of-bounds heap read vulnerability in ImageMagick compiled with TIFF support that can be triggered by running mogrify on crafted TIFF file was found.
Comment 1 Adam Mariš 2016-07-11 08:36:44 EDT
Acknowledgments:

Name: Shi Pu (China Electronic Technology Cyber Security)
Comment 5 Adam Mariš 2016-07-29 08:41:10 EDT
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1361578]
Comment 7 Stefan Cornelius 2018-04-03 19:56:28 EDT
In reply to comment 4:
> Upstream patch:
> 
> http://git.imagemagick.org/repos/ImageMagick/commit/
> c20de102cc57f3739a8870f79e728e3b0bea18c0

Having trouble accessing this, but https://github.com/ImageMagick/ImageMagick/commit/803bc34ebe023f209f745baf8a112610ff77cc8c works and appears to fix this issue.
Comment 8 Stefan Cornelius 2018-04-03 19:56:40 EDT
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.