It is suspected that this package is vulnerable to a security vulnerability in LZO. As such we ask maintainers with packages suspected to be vulnerable to verify if the package is (or have been) affected. Please see the information contained in the tracker bug 515246. "An integer overflow may occur when processing any variant of a "literal run" in the lzo1x_decompress_safe function. Each of these three locations is subject to an integer overflow when processing zero bytes.", additional information about the upstream vulnerability is available at http://seclists.org/oss-sec/2014/q2/665 Reproducible: Didn't try
https://developer.blender.org/T41974
+*blender-2.71-r2 (27 Sep 2014) + + 27 Sep 2014; Julian Ospald <hasufell@gentoo.org> +blender-2.71-r2.ebuild, + +files/04-blender-2.71-r2-unbundle-glog.patch, + +files/09-blender-2.72-unbundle-minilzo.patch: + re-add 2.71 with fixed Manifest wrt #523328 and unbundle minilzo wrt #515266 +*blender-2.72-r1 (27 Sep 2014) + + 27 Sep 2014; Julian Ospald <hasufell@gentoo.org> -blender-2.72.ebuild, + +blender-2.72-r1.ebuild: + unbundle minilzo wrt #515266
+ 16 Dec 2014; Julian Ospald <hasufell@gentoo.org> -blender-2.69-r1.ebuild, + -blender-2.71-r2.ebuild, -blender-2.72-r1.ebuild, + -files/07-blender-2.68-sse2.patch, + -files/02-blender-2.68-unbundle-colamd.patch, + -files/05-blender-2.68-unbundle-eigen3.patch, + -files/04-blender-2.68-unbundle-glog.patch, + -files/04-blender-2.71-r2-unbundle-glog.patch, + -files/09-blender-2.72-unbundle-minilzo.patch: + rm old
why is this bug still open?
Per previous comments maintainer has fixed the upstream LZO issue and the in tree package.
