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.
CVSS Details
- CVSS 3.1 Base Score: 6.5
- CVSS 3.1 Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade imagemagick | Feb 25, 2019 | Sep 7, 2017 |
| Gentoo Linux | — | Upgrade media-gfx/imagemagick. | Nov 13, 2017 | Sep 7, 2017 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Sep 7, 2017 |
| Suse | — | Upgrade libMagick++1Upgrade libMagickWand-6_Q16-1Upgrade libMagick++-develUpgrade libMagickCore-6_Q16-1-32bitUpgrade libMagickCore1Upgrade ImageMagick-develUpgrade ImageMagick-config-6-upstreamUpgrade libMagick++-6_Q16-3Upgrade ImageMagickUpgrade libMagickCore1-32bitUpgrade perl-PerlMagickUpgrade ImageMagick-config-6-SUSEUpgrade libMagickWand1-32bitUpgrade libMagickCore-6_Q16-1Upgrade libMagickWand1 | Dec 20, 2017 | Sep 7, 2017 |
| Ubuntu | — | Upgrade imagemagick-6.q16Upgrade libmagickcore-6.q16-2Upgrade libmagickcore-6.q16-2-extraUpgrade libmagickcore-6.q16-3Upgrade imagemagickUpgrade libmagickcore-6.q16-3-extraUpgrade libmagick++5Upgrade libmagick++-6.q16-5v5Upgrade libmagick++-6.q16-7Upgrade libmagickcore5-extraUpgrade libmagickcore5 | Jun 19, 2018 | Sep 7, 2017 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub