Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Not directly a LibreOffice issue--this is just a safe computing suggestion.

Folks probably should update installed version of the ImageMagick image
utilities. 

Affecting Linux/OS X/Windows flavors.  Has been patched by ImageMagick for
releases > 7.0.1-2 and > 6.9.4-0  so download and upgrade to  a current
build. Available from the project site
http://www.imagemagick.org/script/index.php   (or check for package support
for your distro).

LibreOffice does not install it, rather makes use of ImageMagick when
present as a helper for a number of image filter/conversion actions. 

Stuart

=-ref-=
https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2016-3714

https://www.imagemagick.org/discourse-server/viewtopic.php?f=4&t=29588%29

https://rhn.redhat.com/errata/RHSA-2016-0726.html




--
View this message in context: 
http://nabble.documentfoundation.org/ImageMagick-RCE-exploit-ImageTragick-CVE-2016-3714-tp4183302.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.