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/commit/d9a8234d211da30baf9526fbebe9a8438ea7e11c | Patch Vendor Advisory |
https://github.com/ImageMagick/ImageMagick/issues/712 | Exploit Issue Tracking Patch 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://security.gentoo.org/glsa/201711-07 | Third Party Advisory |
https://usn.ubuntu.com/3681-1/ | Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2017-09-07T06:00:00
Updated: 2020-10-07T19:07:36
Reserved: 2017-09-07T00:00:00
Link: CVE-2017-14175
JSON object: View
NVD Information
Status : Analyzed
Published: 2017-09-07T06:29:00.437
Modified: 2020-10-15T16:07:21.183
Link: CVE-2017-14175
JSON object: View
Redhat Information
No data.
CWE