CVE-2016-5118: Critical severity imagemagick vulnerability
All existing releases of GraphicsMagick and ImageMagick support a file open syntax where if the first character of the file specification is a '|', then the remainder of the filename is passed to the shell for execution using the POSIX popen(3C) function. File opening is handled by an OpenBlob() function in the source file blob.c. Unlike the vulnerability described by CVE-2016-3714, this functionality is supported by the core file opening function rather than a delegates subsystem usually used to execute external programs.
References:
http://seclists.org/oss-sec/2016/q2/432
Other sources
The OpenBlob function in blob.c in GraphicsMagick before 1.3.24 and ImageMagick allows remote attackers to execute arbitrary code via a | (pipe) character at the start of a filename.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2016-5118?
CVE-2016-5118 has a CVSS score indicating it poses a medium severity risk due to command execution vulnerabilities.
How do I fix CVE-2016-5118?
To fix CVE-2016-5118, update to the latest versions of GraphicsMagick and ImageMagick that address this vulnerability.
What types of software are affected by CVE-2016-5118?
CVE-2016-5118 affects multiple software including versions of GraphicsMagick, ImageMagick, and various Linux distributions.
Can CVE-2016-5118 lead to remote code execution?
Yes, CVE-2016-5118 can lead to remote code execution if an attacker exploits the vulnerable file open syntax.
Is there a workaround for CVE-2016-5118 if I cannot update?
A potential workaround for CVE-2016-5118 is to disable or restrict the use of piped file I/O in GraphicsMagick and ImageMagick.