In coders/xbm.c in ImageMagick 7.0.6-1 Q16, a DoS in ReadXBMImage() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted XBM file, which claims large rows and columns fields in the header but does not contain sufficient backing data, is provided, the loop over the rows would consume huge CPU resources, since there is no EOF check inside the loop.
References
Link | Resource |
---|---|
https://github.com/ImageMagick/ImageMagick/issues/712 | Exploit Issue Tracking Patch Third Party Advisory |
https://security.gentoo.org/glsa/201711-07 | Third Party Advisory |
https://usn.ubuntu.com/3681-1/ | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2019/05/msg00015.html | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2020/09/msg00007.html | Third Party Advisory |
https://github.com/ImageMagick/ImageMagick/commit/d9a8234d211da30baf9526fbebe9a8438ea7e11c | Patch Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Information
Published : 2017-09-06 23:29
Updated : 2020-10-15 09:07
NVD link : CVE-2017-14175
Mitre link : CVE-2017-14175
JSON object : View
CWE
CWE-834
Excessive Iteration
Products Affected
debian
- debian_linux
canonical
- ubuntu_linux
imagemagick
- imagemagick