8.1high

CVE-2016-5688

The WPG parser in ImageMagick before 6.9.4-4 and 7.x before 7.0.1-5, when a memory limit is set, allows remote attackers to have unspecifie…

Published 9 y ago · modified 4 mo ago · JSON

CVSS
8.1
v3.0 · NVD
CISA KEV
No
not known exploited
EPSS
4.8%
percentile 92%
Public exploits
0
none known

Summary

The WPG parser in ImageMagick before 6.9.4-4 and 7.x before 7.0.1-5, when a memory limit is set, allows remote attackers to have unspecified impact via vectors related to the SetImageExtent return-value check, which trigger (1) a heap-based buffer overflow in the SetPixelIndex function or an invalid write operation in the (2) ScaleCharToQuantum or (3) SetPixelIndex functions.

Exploit prediction (EPSS)

4.82% probability of exploitation in the next 30 days, higher than 92% of all scored CVEs.

CVSS scores

Assigned byVersionScoreVector
NVD3.08.1CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD2.06.8AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

  • github.com /ImageMagick/ImageMagick/commits/7.0.1-5 · x_refsource_CONFIRM, x_transferred
  • github.com /ImageMagick/ImageMagick/commits/6.9.4-4 · x_refsource_CONFIRM, x_transferred
  • securityfocus.com /bid/91283 · vdb-entry, x_refsource_BID, x_transferred
  • blog.fuzzing-project.org /46-Various-invalid-memory-reads-in-ImageMagick-WPG%2C-DDS%2C-DCM.html · x_refsource_MISC, x_transferred
  • oracle.com /technetwork/topics/security/bulletinjul2016-3090568.html · x_refsource_CONFIRM, x_transferred
  • github.com /ImageMagick/ImageMagick/commit/aecd0ada163a4d6c769cec178955d5f3e9316f2f · x_refsource_CONFIRM, x_transferred
  • openwall.com /lists/oss-security/2016/06/17/3 · mailing-list, x_refsource_MLIST, x_transferred
  • github.com /ImageMagick/ImageMagick/commit/fc43974d34318c834fbf78570ca1a3764ed8c7d7 · x_refsource_CONFIRM, x_transferred
  • openwall.com /lists/oss-security/2016/06/14/5 · mailing-list, x_refsource_MLIST, x_transferred

Sources

vulnwire keeps one entry per vulnerability: the CVE id wins, then GHSA; records that alias each other are merged. Machine-readable: JSON.