ImageMagick does not properly validate input before processing images using a delegate
Original Release date: 04 May 2016 | Last revised: 04 May 2016
ImageMagick does not properly validate user input before processing it using a delegate, which may lead to arbitrary code execution.
This issue is also known as “ImageTragick”.
CWE-20: Improper Input Validation – CVE-2016-3714
According to the researchers in a mailing list post:Insufficient filtering for filename passed to delegate’s command allows remote code execution during conversion of several file formats.ImageMagick allows to process files with external libraries.
This feature is called ‘delegate’.
It is implemented as a system() with command string (‘command’) from the config file delegates.xml with actual value for different params (input/output filenames etc).
Due to insufficient %M param filtering it is possible to conduct shell command injection.By causing a system to process an image with ImageMagick, an attacker may be able to execute arbitrary commands on a vulnerable system. A common vulnerable configuration would be a web server that allows image uploads that are subsequently processed with ImageMagick.Exploit code for this vulnerability is publicly available, and according to the ImageTragick website, this vulnerability is already being exploited in the wild.
An unauthenticated remote attacker that can upload crafted image files may be able to execute arbitrary code in the context of the user calling ImageMagick.
Apply an UpdateImageMagick version 6.9.3-10 and 7.0.1-1 have been released to address these issues.
Affected users should update to the latest version of ImageMagick as soon as possible.However, affected users may also apply the following mitigations:Verify Files and Disable Vulnerable FiltersThe researchers suggest that this vulnerability may be mitigated by doing the following:1.
Verify that all image files begin with the expected “magic bytes” corresponding to the image file types you support before sending them to ImageMagick for processing. 2. Use a policy file to disable the vulnerable ImageMagick coders.
For more details, please see https://imagetragick.com/
Vendor Information (Learn More)
If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
The ImageTragick website credits Stewie and Nikolay Ermishkin of the Mail.Ru Security Team for discovering these vulnerabilities.
This document was written by Garret Wassermann.
03 May 2016
Date First Published:
04 May 2016
Date Last Updated:
04 May 2016
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.