Skip to content
Fencer Intel
medium 6.5

CVE-2017-14139 json

ImageMagick 7.0.6-2 has a memory leak vulnerability in WriteMSLImage in coders/msl.c.

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

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

Summary

ImageMagick 7.0.6-2 has a memory leak vulnerability in WriteMSLImage in coders/msl.c.

Patch / fix

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

debian advisories DEBIAN-CVE-2017-14139

  • ImageMagick SLES for SAP 12 SP3, SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2 +8 more 6.8.8.1-71.42.1

suse advisories SUSE-SU-2018:0581-1

Is CVE-2017-14139 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-14139 updated cvss 3.3

GraphicsMagick: Memory leak in WriteMSLImage function in coders/msl.c

  • 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.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/ImageMagick/ImageMagick/issues/578 referenced PoC, tagged "exploit" by a source, unverified

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:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

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.