In ImageMagick 7.0.8-11 Q16, a tiny input file 0x50 0x36 0x36 0x36 0x36 0x4c 0x36 0x38 0x36 0x36 0x36 0x36 0x36 0x36 0x1f 0x35 0x50 0x00 can result in a hang of several minutes during which CPU and memory resources are consumed until ultimately an attempted large memory allocation fails. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted file.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Imagemagick | Imagemagick | 7.0.8-11-q16 (including) | 7.0.8-11-q16 (including) |
| Red Hat Enterprise Linux 7 | RedHat | autotrace-0:0.31.1-38.el7 | * |
| Red Hat Enterprise Linux 7 | RedHat | emacs-1:24.3-23.el7 | * |
| Red Hat Enterprise Linux 7 | RedHat | ImageMagick-0:6.9.10.68-3.el7 | * |
| Red Hat Enterprise Linux 7 | RedHat | inkscape-0:0.92.2-3.el7 | * |
| Imagemagick | Ubuntu | bionic | * |
| Imagemagick | Ubuntu | cosmic | * |
| Imagemagick | Ubuntu | esm-infra-legacy/trusty | * |
| Imagemagick | Ubuntu | esm-infra/bionic | * |
| Imagemagick | Ubuntu | esm-infra/xenial | * |
| Imagemagick | Ubuntu | trusty | * |
| Imagemagick | Ubuntu | trusty/esm | * |
| Imagemagick | Ubuntu | xenial | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.