CVE-2017-5510

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

coders/psd.c in ImageMagick allows remote attackers to have unspecified impact via a crafted PSD file, which triggers an out-of-bounds write.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
41
EG Risk 41/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.3%
EPSS %ILE
82nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 24, 2017

Last Modified

June 17, 2026

Advisory Details (9)

Auto-updated Sep 30, 2026
Patch available. Sources: github_commit.
generic

[SECURITY] [DSA 3799-1] imagemagick security update

http://www.debian.org/security/2017/dsa-3799
generic

ImageMagick: Multiple vulnerabilities (GLSA 201702-09) — Gentoo security

https://security.gentoo.org/glsa/201702-09
generic

Memory corruption via a PSB file · Issue #348 · ImageMagick/ImageMagick · GitHub

https://github.com/ImageMagick/ImageMagick/issues/348
github_commit

commit e87af64b1ff1 (ImageMagick/ImageMagick)

Fix landed in ImageMagick/ImageMagick commit e87af64b1ff1 — awaiting tagged release

https://github.com/ImageMagick/ImageMagick/commit/e87af64b1ff1635a32d9b6162f1b0e260fb54ed9
github_commit

commit 91cc3f36f2cc (ImageMagick/ImageMagick)

Fix landed in ImageMagick/ImageMagick commit 91cc3f36f2cc — awaiting tagged release

https://github.com/ImageMagick/ImageMagick/commit/91cc3f36f2ccbd485a0456bab9aebe63b635da88
generic Patch Available

#851376 - imagemagick: CVE-2017-5510: coders/psd.c: out-of-bounds write flaw in psd file handling - Debian Bug report logs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851376
generic

CVE-2017-5510 - PSIRT.COM

http://www.securityfocus.com/bid/95755
generic

oss-security - Re: CVE Request: Imagemagick: various flaws: memory corruption, out-of-bounds writes, memory leaks, double-frees, off-by-one errors

http://www.openwall.com/lists/oss-security/2017/01/17/5
generic

oss-security - CVE Request: Imagemagick: various flaws: memory corruption, out-of-bounds writes, memory leaks, double-frees, off-by-one errors

http://www.openwall.com/lists/oss-security/2017/01/16/6

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibmagickcore-6.q16-2-extra (8:6.8.9.9-7ubuntu8.4) @ yakkety2026-05-22ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
imagemagick—
  • every version up to 8:6.9.7.4+dfsg-1: fixed in 8:6.9.7.4+dfsg-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
imagemagick—
  • every version up to 8:6.9.7.4+dfsg-1: fixed in 8:6.9.7.4+dfsg-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
imagemagick—
  • every version up to 8:6.9.7.4+dfsg-1: fixed in 8:6.9.7.4+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
imagemagick—
  • every version up to 8:6.9.7.4+dfsg-1: fixed in 8:6.9.7.4+dfsg-1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
imagemagick8:6.7.7.10-5 ... 8:6.7.7.10-5+deb7u9 (10 versions)
  • every version up to 8:6.7.7.10-5+deb7u11: fixed in 8:6.7.7.10-5+deb7u11
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
imagemagick8:6.8.9.9-5 ... 8:6.8.9.9-5+deb8u6 (7 versions)
  • every version up to 8:6.8.9.9-5+deb8u7: fixed in 8:6.8.9.9-5+deb8u7
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-10-05 17:38 UTCEPSS rescore
  2. 2026-10-03 14:21 UTCEPSS rescore
  3. 2026-09-30 14:59 UTCEPSS rescore
  4. 2026-09-30 09:34 UTCEG score recompute
  5. 2026-09-28 13:45 UTCEPSS rescore
  6. 2026-09-27 13:40 UTCEPSS rescore
  7. 2026-09-27 13:40 UTCEPSS rescore
  8. 2026-09-26 15:53 UTCEPSS rescore
  9. 2026-09-24 13:59 UTCEPSS rescore
  10. 2026-09-18 19:22 UTCEPSS rescore
  11. 2026-09-18 14:06 UTCOSV refresh
  12. 2026-09-17 19:22 UTCEPSS rescore
  13. 2026-09-15 03:05 UTCEPSS rescore
  14. 2026-09-15 03:05 UTCEPSS rescore
  15. 2026-09-12 14:55 UTCEPSS rescore
  16. 2026-09-11 09:31 UTCEPSS rescore
  17. 2026-09-07 15:56 UTCEPSS rescore
  18. 2026-09-06 13:43 UTCEPSS rescore
  19. 2026-09-05 15:23 UTCEPSS rescore
  20. 2026-09-04 13:56 UTCEPSS rescore
  21. 2026-09-02 14:07 UTCEPSS rescore
  22. 2026-09-02 14:07 UTCEPSS rescore
  23. 2026-09-01 03:31 UTCEPSS rescore
  24. 2026-08-30 19:13 UTCEPSS rescore
  25. 2026-08-30 16:21 UTCOSV refresh
Show 75 more
  1. 2026-08-27 14:21 UTCEPSS rescore
  2. 2026-08-26 14:41 UTCEPSS rescore
  3. 2026-08-25 13:44 UTCEPSS rescore
  4. 2026-08-21 23:44 UTCEPSS rescore
  5. 2026-08-20 22:51 UTCEPSS rescore
  6. 2026-08-19 16:59 UTCEPSS rescore
  7. 2026-08-18 13:43 UTCEPSS rescore
  8. 2026-08-17 13:42 UTCEPSS rescore
  9. 2026-08-16 14:51 UTCEPSS rescore
  10. 2026-08-16 02:10 UTCEPSS rescore
  11. 2026-08-15 01:26 UTCEPSS rescore
  12. 2026-08-14 04:19 UTCOSV refresh
  13. 2026-08-12 13:46 UTCEPSS rescore
  14. 2026-08-09 13:42 UTCEPSS rescore
  15. 2026-08-07 16:22 UTCEPSS rescore
  16. 2026-08-06 13:42 UTCEPSS rescore
  17. 2026-08-05 19:12 UTCEPSS rescore
  18. 2026-08-04 15:05 UTCEPSS rescore
  19. 2026-08-02 02:23 UTCEPSS rescore
  20. 2026-08-01 04:11 UTCEPSS rescore
  21. 2026-07-30 16:24 UTCEPSS rescore
  22. 2026-07-30 01:26 UTCEPSS rescore
  23. 2026-07-29 09:04 UTCOSV refresh
  24. 2026-07-28 15:32 UTCEPSS rescore
  25. 2026-07-26 14:51 UTCEPSS rescore
  26. 2026-07-23 14:15 UTCEPSS rescore
  27. 2026-07-23 01:29 UTCEG score recompute
  28. 2026-07-22 22:09 UTCEG score recompute
  29. 2026-07-22 14:04 UTCEPSS rescore
  30. 2026-07-22 14:04 UTCEPSS rescore
  31. 2026-07-21 15:21 UTCEPSS rescore
  32. 2026-07-21 15:21 UTCEPSS rescore
  33. 2026-07-20 17:04 UTCEPSS rescore
  34. 2026-07-19 14:28 UTCEPSS rescore
  35. 2026-07-19 14:28 UTCEPSS rescore
  36. 2026-07-19 02:26 UTCEPSS rescore
  37. 2026-07-19 02:26 UTCEPSS rescore
  38. 2026-07-18 10:00 UTCEPSS rescore
  39. 2026-07-16 16:59 UTCEPSS rescore
  40. 2026-07-16 16:59 UTCEPSS rescore
  41. 2026-07-15 16:54 UTCEPSS rescore
  42. 2026-07-15 01:56 UTCEPSS rescore
  43. 2026-07-15 01:56 UTCEPSS rescore
  44. 2026-07-13 22:26 UTCEPSS rescore
  45. 2026-07-12 05:43 UTCEPSS rescore
  46. 2026-07-12 01:41 UTCOSV refresh
  47. 2026-07-11 08:24 UTCEPSS rescore
  48. 2026-07-09 19:06 UTCEPSS rescore
  49. 2026-07-08 15:10 UTCEPSS rescore
  50. 2026-07-07 13:42 UTCEPSS rescore
  51. 2026-07-06 16:24 UTCEPSS rescore
  52. 2026-07-06 16:24 UTCEPSS rescore
  53. 2026-07-06 02:20 UTCEPSS rescore
  54. 2026-07-06 02:20 UTCEPSS rescore
  55. 2026-07-05 02:27 UTCEPSS rescore
  56. 2026-07-04 06:28 UTCEPSS rescore
  57. 2026-07-02 16:54 UTCEPSS rescore
  58. 2026-07-01 15:02 UTCEPSS rescore
  59. 2026-06-30 23:19 UTCEPSS rescore
  60. 2026-06-30 23:19 UTCEPSS rescore
  61. 2026-06-29 14:03 UTCEPSS rescore
  62. 2026-06-28 14:04 UTCEPSS rescore
  63. 2026-06-28 04:53 UTCEPSS rescore
  64. 2026-06-27 03:06 UTCEPSS rescore
  65. 2026-06-27 03:05 UTCEPSS rescore
  66. 2026-06-25 13:47 UTCEPSS rescore
  67. 2026-06-24 14:02 UTCEPSS rescore
  68. 2026-06-24 14:02 UTCEPSS rescore
  69. 2026-06-23 21:30 UTCEPSS rescore
  70. 2026-06-23 08:00 UTCOSV refresh
  71. 2026-06-22 14:23 UTCEPSS rescore
  72. 2026-06-22 14:23 UTCEPSS rescore
  73. 2026-06-21 14:54 UTCEPSS rescore
  74. 2026-06-21 14:54 UTCEPSS rescore
  75. 2026-06-21 01:57 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-5510?
CVE-2017-5510 is a high vulnerability published on March 24, 2017. coders/psd.c in ImageMagick allows remote attackers to have unspecified impact via a crafted PSD file, which triggers an out-of-bounds write.
When was CVE-2017-5510 disclosed?
CVE-2017-5510 was first published on March 24, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5510 actively exploited?
CVE-2017-5510 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (82nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-5510?
CVE-2017-5510 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2017-5510?
A fix for CVE-2017-5510 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-5510

Explore →

Is Your Infrastructure Affected by CVE-2017-5510?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs