4 ms·
I've been using GraphicsMagick for a while now. Is that also affected or is it just waiting to be checked for the same bugs?
by cm3 10y ago
I've been using GraphicsMagick for a while now. Is that also affected or is it just waiting to be checked for the same bugs?
- alexkavon 10y ago+1 to this. I use GraphicsMagick too and it would be great to know.
- caseyf 10y agoNo idea, but I'd assume yes for the time being. The Graphicsmagick code base includes 3 of the 5 coders that are mentioned (URL, MVG and MSL). 2 of those use LibXML and url.c suspiciously uses LibXML's nanoftp and nanohttp.
- xDranik 10y agoAny idea how to disable those coders with GraphicsMagick? ImageMagick supports a policy file to disable coders (mentioned here https://imagetragick.com/ https://imagetragick.com/). Would need to do the same for GraphicsMagick
- adrianmacneil 10y agoGeneral consensus so far seems to be that GraphicsMagick is unaffected by this vulnerability. If security is really important to you though, you should move image processing to separate isolated servers anyway, and verify magic bytes as described by this site.
- caseyf 10y agoQuick update: None of the 5 PoCs that were published work on GraphicsMagick for me. I was checking magic numbers before sending files to GraphicsMagick but I'm going to go through my code again and make sure that this is always happening.
- atilimcetin 10y agodelegates.mgk.in file of GraphicsMagick contains this comment: Under Unix, all text (non-numeric) substitutions should be surrounded with double quotes for the purpose of security, and because any double quotes occuring within the substituted text will be escaped using a backslash. Commands (excluding file names) containing one or more of the special characters ";&|><" (requiring that multiple processes be executed) are executed via the Unix shell with text substitutions carefully excaped to avoid possible compromise. Otherwise, commands are executed directly without use of the Unix shell. I assume GraphicsMagick doesn't suffer from this vulnerability.
- tyingq 10y agoPerhaps not the unescaped shell characters, but that's not the only hole that was found.