Back to bug 26019

Who When What Removed Added
luigiwalser 2020-01-05 04:34:17 CET Whiteboard MGA7TOO
luigiwalser 2020-01-14 17:35:52 CET Status comment Fixed upstream in 4.1.42
luigiwalser 2020-02-19 23:24:43 CET Status comment Fixed upstream in 4.1.42 Fixed upstream in 4.1.44
Summary netty new security issue CVE-2019-16869 netty new security issue CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-7238
luigiwalser 2020-09-22 19:31:19 CEST Severity major critical
Summary netty new security issue CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-7238 netty, netty3 new security issues CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-7238, CVE-2020-11612
Status comment Fixed upstream in 4.1.44 Fixed upstream in 4.1.46
Source RPM netty-4.1.13-2.mga8.src.rpm netty-4.1.13-2.mga8.src.rpm, netty3-3.10.6-4.mga8.src.rpm
luigiwalser 2020-12-15 17:02:59 CET CC zombie_ryushu
mageia 2020-12-27 00:34:22 CET Version Cauldron 7
CC mageia
Whiteboard MGA7TOO
luigiwalser 2020-12-27 00:40:10 CET Source RPM netty-4.1.13-2.mga8.src.rpm, netty3-3.10.6-4.mga8.src.rpm netty-4.1.13-1.mga7.src.rpm, netty3-3.10.6-2.mga7.src.rpm
luigiwalser 2021-02-26 17:13:19 CET Summary netty, netty3 new security issues CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-7238, CVE-2020-11612 netty, netty3 new security issues CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-7238, CVE-2020-11612, CVE-2021-21290
Status comment Fixed upstream in 4.1.46 Fixed upstream in 4.1.59
luigiwalser 2021-02-26 17:14:10 CET Depends on 28446
luigiwalser 2021-05-28 22:10:17 CEST Depends on 28985
luigiwalser 2021-05-28 22:10:48 CEST Status comment Fixed upstream in 4.1.59 Fixed upstream in 4.1.61
Summary netty, netty3 new security issues CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-7238, CVE-2020-11612, CVE-2021-21290 netty, netty3 new security issues CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-7238, CVE-2020-11612, CVE-2021-21290, CVE-2021-21295, CVE-2021-21409
luigiwalser 2021-07-01 18:21:11 CEST Resolution --- OLD
Status NEW RESOLVED

Back to bug 26019