ImageMagick vulnerable to heap-buffer-overflow

md

Analysis

ImageMagick versions 7.1.1-13 and earlier contain a heap-buffer-overflow vulnerability when processing specially crafted TIFF files. The bug is triggered in the TIFF decoding routines, leading to memory corruption and an application crash. [2][3]

Exploitation

An attacker can exploit this vulnerability by providing a malicious TIFF file to an application or service that uses ImageMagick, such as a web upload feature or image processing pipeline. No authentication is required; the attacker only needs to induce the target to process the file, e.g., via magick poc.tiff /dev/null. [1][3]

ImpactSuccessful exploitation leads to a denial-of-service condition (application crash). Based on the available information, there is no further code execution or data leakage is proven, but heap overflows can potentially be leveraged for more severe impacts depending on memory layout and mitigations. [3]

MitigationThe vulnerability is fixed in

ImageMagick version 7.1.1-14 and later. Users should upgrade immediately or implement a security policy to restrict processing of untrusted TIFF files as a workaround. [2][3]