CVE-2016-8862: Buffer Overflow

Published Oct 20, 2016
·
Updated

A memory allocation failure was found in ImageMagick in memory.c

References:

http://seclists.org/oss-sec/2016/q4/167 https://blogs.gentoo.org/ago/2016/10/17/imagemagick-memory-allocation-failure-in-acquiremagickmemory-memory-c/

Upstream patch:

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

Other sources

The AcquireMagickMemory function in MagickCore/memory.c in ImageMagick before 7.0.3.3 allows remote attackers to have unspecified impact via a crafted image, which triggers a memory allocation failure.

MITRE

Affected Software

4 affected componentsFixes available
redhat/ImageMagick<7.0.3.3
7.0.3.3
ImageMagick ImageMagick<6.9.4-0
ImageMagick ImageMagick>=7.0.0-0<7.0.3-3
Debian Debian Linux=8.0

Event History

Feb 15, 2017
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Data Sourced
via NVD·07:59 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2016-8862?

CVE-2016-8862 is classified as a moderate severity vulnerability due to its potential impact on memory management in ImageMagick.

2

How do I fix CVE-2016-8862?

To fix CVE-2016-8862, upgrade ImageMagick to version 7.0.3.3 or later, or if using version 6.x, ensure it is updated to any version above 6.9.4-0.

3

What are the affected versions for CVE-2016-8862?

CVE-2016-8862 affects ImageMagick versions prior to 7.0.3.3 and versions from 7.0.0-0 up to 7.0.3-3.

4

What causes CVE-2016-8862?

CVE-2016-8862 is caused by a memory allocation failure in the ImageMagick library.

5

Is CVE-2016-8862 present in Debian systems?

Yes, CVE-2016-8862 can affect Debian systems running ImageMagick versions before the patched releases.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203