Skip to content
Fencer Intel
high 8.8

CVE-2014-2030 in the critical feed json

Stack-based buffer overflow in the WritePSDImage function in coders/psd.c in ImageMagick, possibly 6.8.8-5, allows remote attackers to caus…

published 2020-02-06 6 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2082

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
11.1%
EPSS 11.1% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Stack-based buffer overflow in the WritePSDImage function in coders/psd.c in ImageMagick, possibly 6.8.8-5, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted PSD image, involving the L%06ld string, a different vulnerability than CVE-2014-1947.

Patch / fix

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-2014-2030 updated cvss 6.8

ImageMagick: PSD writing layer name buffer overflow ("L%06ld")

  • Red Hat OpenShift Enterprise 1 ImageMagick 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
    not affected: vulnerable code not present

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

Timeline

  1. First public exploit (EDB-31688)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-31688 ImageMagick 6.8.8-4 - Local Buffer Overflow (SEH) local, 2014-02-16

CVSS scores

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

Classification

Weakness

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.