Skip to content
Fencer Intel
medium 6.5

CVE-2017-11536 json

When ImageMagick 7.0.6-1 processes a crafted file in convert, it can lead to a Memory Leak in the WriteJP2Image() function in coders/jp2.c.

published 9y ago modified 4mo ago also EUVD-2017-3152

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

When ImageMagick 7.0.6-1 processes a crafted file in convert, it can lead to a Memory Leak in the WriteJP2Image() function in coders/jp2.c.

Patch / fix

  • imagemagick Debian 14, Debian 13, Debian 12 8:6.9.7.4+dfsg-13

debian advisories DEBIAN-CVE-2017-11536

Is CVE-2017-11536 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-11536 updated cvss 3.3

ImageMagick: Memory leak in the WriteJP2Image() function

  • Red Hat Enterprise Linux 5 ImageMagick Red Hat Enterprise Linux 6 ImageMagick, ImageMagick-c++, ImageMagick-perl Red Hat Enterprise Linux 7 ImageMagick, ImageMagick-c++, ImageMagick-perl Red Hat OpenShift Enterprise 2 ImageMagick
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.42% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-772 Missing Release of Resource after Effective Lifetime

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.