CVE-2017-14175

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.

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.

En coders/xbm.c en ImageMagick 7.0.6-1 Q16, una denegación de servicio en ReadXBMImage() por una falta de chequeos EOF (End of File) podría provocar un enorme consumo de recursos de la CPU. Cuando se proporciona un archivo XBM manipulado que pide campos de columnas y filas grandes en la cabecera pero no contiene suficientes datos de respaldo, el bucle en las filas consumiría una gran cantidad de recursos de CPU, ya que el bucle no contiene ningún chequeo EOF.