CVE-2017-6501 json
An issue was discovered in ImageMagick 6.9.7.
published 2017-03-06 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-15557
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
An issue was discovered in ImageMagick 6.9.7. A specially crafted xcf file could lead to a NULL pointer dereference.
Patch / fix
- imagemagick Debian 14, Debian 13, Debian 12 8:6.9.7.4+dfsg-2
debian advisories DEBIAN-CVE-2017-6501
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-6501 updated cvss 3.3
ImageMagick: NULL pointer dereference in xcf.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 ImageMagickaffected: 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.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/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-476 NULL Pointer Dereference
References
-
github.com
/ImageMagick/ImageMagick/commit/d31fec57e9dfb0516deead2053a856e3c71e9751
patch
-
securityfocus.com
/bid/96589
vdb-entry, third-party-advisory
-
bugs.debian.org
/856881
issue-tracking, mailing-list, third-party-advisory
Sources
- CVE List CVE-2017-6501
- NVD CVE-2017-6501
Fencer Vulns 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.