How severe is CVE-2017-11450?

CVE-2017-11450 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-11450 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-11450?

CVE-2017-11450 primarily affects Imagemagick. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-11450?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-11450 published?

CVE-2017-11450 was published on 2017-07-19 and last updated on 2026-06-17.

CVE-2017-11450

CVE-2017-11450 is a high-severity vulnerability in Imagemagick with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.8
EPSS exploit prediction: 2% (82nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Imagemagick
Published: 2017-07-19
Last modified: 2026-06-17

Description

coders/jpeg.c in ImageMagick before 7.0.6-1 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via JPEG data that is too short.

Frequently asked questions

What is CVE-2017-11450?: coders/jpeg.c in ImageMagick before 7.0.6-1 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via JPEG data that is too short.
How severe is CVE-2017-11450?: CVE-2017-11450 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-11450 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-11450?: CVE-2017-11450 primarily affects Imagemagick. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-11450?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-11450 published?: CVE-2017-11450 was published on 2017-07-19 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:imagemagick:imagemagick:*:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

More vulnerabilities in Imagemagick

CVE-2004-0981 — Critical (CVSS 10.0): Buffer overflow in the EXIF parsing routine in ImageMagick before 6.1.0 allows remote attackers to execute arbitrary…
CVE-2023-34152 — Critical (CVSS 9.8): A vulnerability was found in ImageMagick. This security flaw cause a remote code execution vulnerability in OpenBlob…
CVE-2019-19952 — Critical (CVSS 9.8): In ImageMagick 7.0.9-7 Q16, there is a use-after-free in the function MngInfoDiscardObject of coders/png.c, related to…
CVE-2019-19948 — Critical (CVSS 9.8): In ImageMagick 7.0.8-43 Q16, there is a heap-based buffer overflow in the function WriteSGIImage of coders/sgi.c.
CVE-2018-16329 — Critical (CVSS 9.8): In ImageMagick before 7.0.8-8, a NULL pointer dereference exists in the GetMagickProperty function in…
CVE-2018-16328 — Critical (CVSS 9.8): In ImageMagick before 7.0.8-8, a NULL pointer dereference exists in the CheckEventLogging function in MagickCore/log.c.

All CVEs affecting Imagemagick →