ImageMagick: Lack of EOF check in the ReadXBMImage() function
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1131-1 | imagemagick security update |
Debian DLA |
DLA-1785-1 | imagemagick security update |
Debian DLA |
DLA-2366-1 | imagemagick security update |
EUVD |
EUVD-2017-5685 | 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. |
Ubuntu USN |
USN-3681-1 | ImageMagick vulnerabilities |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 2.1% (2.122% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.