Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1388816 - (CVE-2016-8866) CVE-2016-8866 ImageMagick: Memory allocation failure in AcquireMagickMemory (incomplete fix for CVE-2016-8862)
CVE-2016-8866 ImageMagick: Memory allocation failure in AcquireMagickMemory (...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161020,repor...
: Security
Depends On: 1381145
Blocks: 1381146
  Show dependency treegraph
 
Reported: 2016-10-26 04:44 EDT by Andrej Nemec
Modified: 2017-11-21 00:25 EST (History)
14 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-21 00:25:01 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)

  None (edit)
Description Andrej Nemec 2016-10-26 04:44:14 EDT
It was discovered that the upstream fix for this issue was not complete. There is still a memory allocation failure in memory.c

References:

http://seclists.org/oss-sec/2016/q4/197
https://blogs.gentoo.org/ago/2016/10/20/imagemagick-memory-allocation-failure-in-acquiremagickmemory-memory-c-incomplete-fix-for-cve-2016-8862/
Comment 1 Andrej Nemec 2016-10-26 04:47:47 EDT
Created ImageMagick tracking bugs for this issue:

Affects: fedora-all [bug 1381145]
Comment 2 Huzaifa S. Sidhpurwala 2017-01-20 03:44:16 EST
Upstream patch:

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

Analysis:

Basically lowers map_length from 32 (fix for CVE-2016-8862) to the new value 22. Even without the previous fix, this flaw affects ImageMagick shipped with Red Hat Enterprise Linux, hence marking as affected.

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