First published: Wed Jun 20 2018(Updated: )
A flaw was found in ImageMagick 7.0.8-3 Q16, ReadBMPImage and WriteBMPImage in coders/bmp.c allow attackers to cause an out of bounds write via a crafted file. References: <a href="https://github.com/ImageMagick/ImageMagick/issues/1177">https://github.com/ImageMagick/ImageMagick/issues/1177</a> Patch: <a href="https://github.com/ImageMagick/ImageMagick6/commit/081f518eb9cb38e683b8b9ccb9e4ab5c52f82c2f">https://github.com/ImageMagick/ImageMagick6/commit/081f518eb9cb38e683b8b9ccb9e4ab5c52f82c2f</a> <a href="https://github.com/ImageMagick/ImageMagick/commit/ae04fa4be910255e5d363edebd77adeee99a525d">https://github.com/ImageMagick/ImageMagick/commit/ae04fa4be910255e5d363edebd77adeee99a525d</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Data Risk Manager | <=2.0.6 | |
ubuntu/imagemagick | <8:6.9.7.4+dfsg-16ubuntu2.3 | 8:6.9.7.4+dfsg-16ubuntu2.3 |
ubuntu/imagemagick | <8:6.9.7.4+dfsg-16ubuntu6.3 | 8:6.9.7.4+dfsg-16ubuntu6.3 |
ubuntu/imagemagick | <8:6.7.7.10-6ubuntu3.12 | 8:6.7.7.10-6ubuntu3.12 |
ubuntu/imagemagick | <8:6.8.9.9-7ubuntu5.12 | 8:6.8.9.9-7ubuntu5.12 |
debian/imagemagick | 8:6.9.11.60+dfsg-1.3+deb11u3 8:6.9.11.60+dfsg-1.6+deb12u1 8:6.9.13.12+dfsg1-1 | |
Ubuntu Linux | =14.04 | |
Ubuntu Linux | =16.04 | |
Ubuntu Linux | =17.10 | |
Ubuntu Linux | =18.04 | |
Debian | =8.0 | |
Debian | =9.0 | |
ImageMagick | =7.0.8-3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-12599 has been rated as a medium severity vulnerability due to the potential for out-of-bounds write attacks.
To address CVE-2018-12599, update ImageMagick to version 7.0.8-4 or later where the vulnerability is patched.
CVE-2018-12599 affects ImageMagick versions up to and including 7.0.8-3, specifically impacting BMP file handling.
Yes, CVE-2018-12599 can be exploited remotely through crafted BMP files uploaded to a vulnerable server.
If your system is using ImageMagick version 7.0.8-3 or earlier, it is vulnerable to CVE-2018-12599 and should be updated immediately.