First published: Wed Oct 26 2016(Updated: )
It was discovered that the upstream fix for this issue was not complete. There is still a memory allocation failure in memory.c References: <a href="http://seclists.org/oss-sec/2016/q4/197">http://seclists.org/oss-sec/2016/q4/197</a> <a href="https://blogs.gentoo.org/ago/2016/10/20/imagemagick-memory-allocation-failure-in-acquiremagickmemory-memory-c-incomplete-fix-for-cve-2016-8862/">https://blogs.gentoo.org/ago/2016/10/20/imagemagick-memory-allocation-failure-in-acquiremagickmemory-memory-c-incomplete-fix-for-cve-2016-8862/</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
ImageMagick | <6.9.6-6 | |
ImageMagick | >=7.0.0-0<=7.0.3-7 | |
SUSE Linux | =42.1 | |
SUSE Linux | =42.2 | |
SUSE Linux | =13.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2016-8866 is considered important due to the potential for memory allocation failures.
To fix CVE-2016-8866, you should upgrade to the latest version of ImageMagick that addresses this vulnerability.
Applications affected by CVE-2016-8866 include certain versions of ImageMagick and specific openSUSE releases.
Yes, CVE-2016-8866 is related to CVE-2016-8862 as it pertains to a similar memory allocation issue.
CVE-2016-8866 was discovered as part of an upstream fix that was incomplete, leading to a memory allocation failure.