CVE-2018-14551 json
The ReadMATImageV4 function in coders/mat.c in ImageMagick 7.0.8-7 uses an uninitialized variable, leading to memory corruption.
published 8y ago modified 4mo ago also EUVD-2018-6460
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
The ReadMATImageV4 function in coders/mat.c in ImageMagick 7.0.8-7 uses an uninitialized variable, leading to memory corruption.
Patch / fix
- imagemagick Debian 14, Debian 13, Debian 12 8:6.9.10.8+dfsg-1
debian advisories DEBIAN-CVE-2018-14551
- imagemagick Ubuntu 18.04 LTS 8:6.9.7.4+dfsg-16ubuntu6.4
ubuntu advisories UBUNTU-CVE-2018-14551
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- imagemagick6 Alpine 3.16, Alpine 3.15, Alpine 3.14 +4 more 6.9.10.37-r0
- imagemagick6 Alpine 3.9, Alpine 3.8, Alpine 3.7 6.9.10.39-r0
alpine advisories ALPINE-CVE-2018-14551
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2018-14551 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-14551 updated cvss 4.3
ImageMagick: Uninitialized variable in coders/mat.c:ReadMATImageV4() allows for memory corruption
-
Red Hat Enterprise Linux 8 ImageMagickaffected: no fix planned “Will not fix”
-
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-perlnot 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
Exploit prediction
4.03% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/ImageMagick/ImageMagick/issues/1221 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
References
-
github.com
/ImageMagick/ImageMagick/issues/1221
exploit, third-party-advisory
-
usn.ubuntu.com
/3785-1/
vendor-advisory, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2020/08/msg00030.html
mailing-list
Sources
- CVE List CVE-2018-14551
- NVD CVE-2018-14551
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.