CVE-2017-16353 json
GraphicsMagick 1.3.26 is vulnerable to a memory information disclosure vulnerability found in the DescribeImage function of the magick/desc…
published 2017-11-01 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-7548
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.7%
- EPSS 13.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
GraphicsMagick 1.3.26 is vulnerable to a memory information disclosure vulnerability found in the DescribeImage function of the magick/describe.c file, because of a heap-based buffer over-read. The portion of the code containing the vulnerability is responsible for printing the IPTC Profile information contained in the image. This vulnerability can be triggered with a specially crafted MIFF file. There is an out-of-bounds buffer dereference because certain increments are never checked.
Patch / fix
- graphicsmagick Debian 14, Debian 13, Debian 12 1.3.26-17
debian advisories DEBIAN-CVE-2017-16353
- graphicsmagick Ubuntu 16.04 LTS 1.3.23-1ubuntu0.4
- graphicsmagick Ubuntu Pro 14.04 LTS 1.3.18-1ubuntu3.1+esm4
ubuntu advisories UBUNTU-CVE-2017-16353
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
- ImageMagick SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 6.4.3.6-78.40.1
- GraphicsMagick Studio Onsite 1.3, SLE Software Development Kit 11 SP4 1.2.5-78.44.1
- ImageMagick SLES for SAP 12 SP3, SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2 +8 more 6.8.8.1-71.47.1
suse advisories SUSE-SU-2018:0880-1SUSE-SU-2018:0864-1SUSE-SU-2018:0857-1
- graphicsmagick Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 1.3.27-r0
alpine advisories ALPINE-CVE-2017-16353
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
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-16353 updated cvss 3.3
GraphicsMagick: memory information disclosure in DescribeImage function in magick/describe.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-perlaffected: 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
Timeline
- Published
- First public exploit (EDB-43111)
Exploit prediction
13.68% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-43111 GraphicsMagick - Memory Disclosure / Heap Overflow dos, 2017-11-03
- blogs.securiteam.com https://blogs.securiteam.com/index.php/archives/3494 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
References
-
exploit-db.com
/exploits/43111/
exploit, third-party-advisory, vdb-entry
-
blogs.securiteam.com
/index.php/archives/3494
exploit, third-party-advisory
-
debian.org
/security/2018/dsa-4321
vendor-advisory, third-party-advisory
-
usn.ubuntu.com
/4232-1/
vendor-advisory
- hg.graphicsmagick.org /hg/GraphicsMagick?cmd=changeset%3Bnode=e4e1c2a581d8
-
securityfocus.com
/bid/101653
vdb-entry, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2018/06/msg00009.html
mailing-list, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2017/11/msg00002.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2017-16353
- NVD CVE-2017-16353
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.