2 ms·
http://www.imagemagick.org/script/convert.php http://www.imagemagick.org/script/convert.php You can insert ImageMagick somewhere into your production pipeline.
by criddell 10y ago
http://www.imagemagick.org/script/convert.php http://www.imagemagick.org/script/convert.php
You can insert ImageMagick somewhere into your production pipeline. It's excellent software.
- lmm 10y agoWell other than being riddled with security holes. It has its place, but never use it on user-submitted images.
- microcolonel 10y agoWhile that may have been true in 2014, today it's hard to find an exploitable bug affecting a major image format parser in ImageMagick. Assuming you aren't using unsanitized user-provided parameters on the command line with it, it should be fine unless your attacker is very motivated.
- nitrogen 10y agoThere was an RCE vulnerability this year: https://imagetragick.com/ https://imagetragick.com/
- tetromino_ 10y agoImageTragick did not affect major image formats; it was a vulnerability in the parser for ImageMagick's scripting languages [1]. The real problem was that support for scripting was enabled by default, and there was no obvious big red button to disable it. [1] Like MVG (http://www.imagemagick.org/script/magick-vector-graphics.php http://www.imagemagick.org/script/magick-vector-graphics.php) and MSL (http://www.imagemagick.org/script/conjure.php http://www.imagemagick.org/script/conjure.php)
- criddell 10y agoWell, the person I'm responding to is using Photoshop to resize images. Presumably that isn't for user submitted content.
- Veratyr 10y agoI'd argue that you should simply sandbox it. If performance is an issue, throw it in a VM or container with a simple socat + fork + TCP-LISTEN on a socket and pipe data in/out over TCP.