From ${URL} : * Several integer overflows: Report: https://bugs.chromium.org/p/webp/issues/detail?id=314 (private) Fix: https://chromium.googlesource.com/webm/libwebp/+/e2affacc35f1df6cc3b1a9fa0ceff5ce2d0cce83 @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
There is also: * NULL pointer derreference Bug report: https://bugs.chromium.org/p/webp/issues/detail?id=310 (private) Fix: https://chromium.googlesource.com/webm/libwebp/+/806f6279aef4de8deca01c8e727db4a508716e95 which did not receive a CVE but would be great to have the fix in the tree.
Fixed via https://github.com/webmproject/libwebp/commit/bb23361 and https://github.com/webmproject/libwebp/commit/883d41f @ Maintainer(s): Can we start stabilization of =media-libs/libwebp-0.5.2?
No objection from me.
@ Arches, please test and mark stable: =media-libs/libwebp-0.5.2
amd64 stable
x86 stable
sparc stable
(In reply to Mike Gilbert from comment #3) > No objection from me. You checked for open bugs against the package?
arm stable
Stable for HPPA.
(In reply to Jeroen Roovers from comment #8) > You checked for open bugs against the package? Yes, and I saw an unconfirmed bug report for an issue that only occurs with stupid CFLAGS.
(In reply to Mike Gilbert from comment #11) > (In reply to Jeroen Roovers from comment #8) > > You checked for open bugs against the package? > > Yes, and I saw an unconfirmed bug report for an issue that only occurs with > stupid CFLAGS. 1. It's unconfirmed so it needed further investigation, which could easily be done by using the CFLAGS from the bug report to reproduce the issue. 2. Since the fix was to employ some configure flags that were helpfully put in place upstream already, upstream apparently don't regard them as "stupid" like you do. 3. I can CC and un-CC myself. You don't need to do anything. Please don't.
ppc stable
(In reply to Jeroen Roovers from comment #12) Sorry for my flippant response. > I can CC and un-CC myself. You don't need to do anything. Please don't. I copied you so that you would see my response, that's all.
Stable on alpha.
ia64 stable
ppc64 stable. Maintainer(s), please cleanup. Security, please add it to the existing request, or file a new one.
GLSA request filed.
This issue was resolved and addressed in GLSA 201701-61 at https://security.gentoo.org/glsa/201701-61 by GLSA coordinator Aaron Bauman (b-man).
re-opened for cleanup
Maintainer(s), please drop the vulnerable version(s).
Done.
Repository is clean, all done. @ Arches and Maintainer(s): Thank you for your work.
