https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:33:30 +0000 https://cve.radiocsirt.org/vuln/bdu:2017-02082 bdu:2017-02082 https://cve.radiocsirt.org/vuln/bdu:2017-02082 https://cve.radiocsirt.org/vuln/cnvd-2017-31330 cnvd-2017-31330 https://cve.radiocsirt.org/vuln/cnvd-2017-31330 https://cve.radiocsirt.org/vuln/euvd-2026-77874 EUVD-2026-77874 https://cve.radiocsirt.org/vuln/euvd-2026-77874 https://cve.radiocsirt.org/vuln/fkie_cve-2017-14175 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2017-14175 https://cve.radiocsirt.org/vuln/ghsa-2g4j-2xqp-4hq5 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-2g4j-2xqp-4hq5 https://cve.radiocsirt.org/vuln/gsd-2017-14175 gsd-2017-14175 https://cve.radiocsirt.org/vuln/gsd-2017-14175 https://cve.radiocsirt.org/vuln/suse-su-2017:3378-1 <p>Security update for ImageMagick</p> <p>Security update for ImageMagick</p> https://cve.radiocsirt.org/vuln/suse-su-2017:3378-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-14175 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: imagemagick, Ubuntu:16.04:LTS: imagemagick, Ubuntu:18.04:LTS: imagemagick</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: imagemagick, Ubuntu:16.04:LTS: imagemagick, Ubuntu:18.04:LTS: imagemagick</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-14175