CVE-2017-16353 Details
Description
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.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-125 | Out-of-bounds Read | [email protected] |
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| graphicsmagick graphicsmagick | 1.3.26 |
CPE
Remediation
| |
| debian debian linux | 7.0 8.0 9.0 |
CPE
Remediation
| |
Change History
13 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| May 13, 2026 | CVE Status Change | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Nov 7, 2023 | CVE Modified | [email protected] |
| Jan 8, 2020 | CVE Modified | [email protected] |
| Mar 8, 2019 | Modified Analysis | [email protected] |
| Oct 18, 2018 | CVE Modified | [email protected] |
| Jun 29, 2018 | CVE Modified | [email protected] |
| Feb 4, 2018 | CVE Modified | [email protected] |
| Nov 13, 2017 | Initial Analysis | [email protected] |
| Nov 6, 2017 | CVE Modified | [email protected] |
| Nov 4, 2017 | CVE Modified | [email protected] |