Back to bug 29972
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| luigiwalser | 2022-01-30 19:27:47 CET | Status comment | Fixed upstream in 8.2.4227 | |
| lewyssmith | 2022-01-30 21:42:51 CET | Assignee | bugsquad | thierry.vignaud |
| luigiwalser | 2022-02-04 16:27:52 CET | Summary | vim new security issues CVE-2022-0261 and CVE-2022-035[19] | vim new security issues CVE-2022-0261 and CVE-2022-035[189] |
| luigiwalser | 2022-02-11 21:57:15 CET | Status comment | Fixed upstream in 8.2.4227 | Fixed upstream in 8.2.4286 |
| Summary | vim new security issues CVE-2022-0261 and CVE-2022-035[189] | vim new security issues CVE-2022-0261, CVE-2022-035[189], CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443 | ||
| luigiwalser | 2022-02-17 19:04:11 CET | Summary | vim new security issues CVE-2022-0261, CVE-2022-035[189], CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443 | vim new security issues CVE-2022-0261, CVE-2022-035[189], CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443, CVE-2022-0572 |
| luigiwalser | 2022-02-23 18:47:46 CET | Summary | vim new security issues CVE-2022-0261, CVE-2022-035[189], CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443, CVE-2022-0572 | vim new security issues CVE-2022-0261, CVE-2022-035[189], CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443, CVE-2022-0572, CVE-2022-0629 |
| Status comment | Fixed upstream in 8.2.4286 | Fixed upstream in 8.2.4428 | ||
| luigiwalser | 2022-02-26 16:49:18 CET | Summary | vim new security issues CVE-2022-0261, CVE-2022-035[189], CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443, CVE-2022-0572, CVE-2022-0629 | vim new security issues CVE-2022-0261, CVE-2022-035[189], CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443, CVE-2022-0554, CVE-2022-0572, CVE-2022-0629, CVE-2022-0685, CVE-2022-0696, CVE-2022-0714, CVE-2022-0729 |
| Status comment | Fixed upstream in 8.2.4428 | Fixed upstream in 8.2.4460 | ||
| luigiwalser | 2022-03-04 19:42:51 CET | Summary | vim new security issues CVE-2022-0261, CVE-2022-035[189], CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443, CVE-2022-0554, CVE-2022-0572, CVE-2022-0629, CVE-2022-0685, CVE-2022-0696, CVE-2022-0714, CVE-2022-0729 | vim new security issues CVE-2022-0261, CVE-2022-031[89], CVE-2022-035[189],CVE-2022-0361,CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443, CVE-2022-0554, CVE-2022-0572, CVE-2022-0629, CVE-2022-0685, CVE-2022-0696, CVE-2022-0714, CVE-2022-0729 |
| luigiwalser | 2022-03-29 15:29:56 CEST | CVE | CVE-2022-0943 | |
| Status comment | Fixed upstream in 8.2.4460 | Fixed upstream in 8.2.4563 | ||
| luigiwalser | 2022-04-09 19:31:15 CEST | CVE | CVE-2022-0943 | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160 |
| Status comment | Fixed upstream in 8.2.4563 | Fixed upstream in 8.2.4647 | ||
| luigiwalser | 2022-04-24 18:17:23 CEST | Status comment | Fixed upstream in 8.2.4647 | Fixed upstream in 8.2.4774 |
| CVE | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160 | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420 | ||
| luigiwalser | 2022-05-11 20:20:58 CEST | Status comment | Fixed upstream in 8.2.4774 | Fixed upstream in 8.2.4901 |
| CVE | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420 | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-1620 | ||
| luigiwalser | 2022-05-17 15:43:50 CEST | Status comment | Fixed upstream in 8.2.4901 | Fixed upstream in 8.2.4919 |
| CVE | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-1620 | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[01] | ||
| luigiwalser | 2022-05-18 20:26:59 CEST | Status comment | Fixed upstream in 8.2.4919 | Fixed upstream in 8.2.4925 |
| CVE | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[01] | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019] | ||
| luigiwalser | 2022-05-19 19:01:42 CEST | Status comment | Fixed upstream in 8.2.4925 | Fixed upstream in 8.2.4938 |
| CVE | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019] | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019], CVE-2022-1674 | ||
| mageia | 2022-05-22 07:49:34 CEST | Assignee | thierry.vignaud | qa-bugs |
| CC | mageia, thierry.vignaud | |||
| mageia | 2022-05-22 07:49:40 CEST | Status comment | Fixed upstream in 8.2.4938 | |
| tarazed25 | 2022-05-23 08:34:28 CEST | CC | tarazed25 | |
| Whiteboard | MGA8-64-OK | |||
| andrewsfarm | 2022-05-23 14:03:59 CEST | CC | andrewsfarm, sysadmin-bugs | |
| Keywords | validated_update | |||
| luigiwalser | 2022-05-23 20:11:42 CEST | CVE | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019], CVE-2022-1674 | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019], CVE-2022-1674, CVE-2022-1769, CVE-2022-1733 |
| davidwhodgins | 2022-05-25 02:25:12 CEST | CC | davidwhodgins | |
| Keywords | advisory | |||
| bot | 2022-05-25 20:47:32 CEST | Resolution | --- | FIXED |
| Status | NEW | RESOLVED | ||
| luigiwalser | 2022-06-02 23:54:30 CEST | Summary | , CVE-2022-0729 vim new security issues CVE-2022-0261, CVE-2022-031[89], CVE-2022-035[189],CVE-2022-0361,CVE-2022-0393, CVE-2022-0408, CVE-2022-041[37], CVE-2022-0443, CVE-2022-0554, CVE-2022-0572, CVE-2022-0629, CVE-2022-0685, CVE-2022-0696, CVE-2022-0714 | , CVE-2022-0729 vim new security issues CVE-2022-0261, CVE-2022-031[89], CVE-2022-035[189],CVE-2022-036[18],CVE-2022-0393,CVE-2022-0408,CVE-2022-041[37],CVE-2022-0443, CVE-2022-0554, CVE-2022-0572, CVE-2022-0629, CVE-2022-0685, CVE-2022-0696, CVE-2022-0714 |
| luigiwalser | 2022-06-30 19:58:08 CEST | Summary | , CVE-2022-0729 | |
| CVE | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019], CVE-2022-1674, CVE-2022-1769, CVE-2022-1733 | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019], CVE-2022-1674, CVE-2022-1720, CVE-2022-173[35], CVE-2022-1769, CVE-2022-1771 | ||
| Summary | vim new security issues CVE-2022-0261, CVE-2022-031[89], CVE-2022-035[189],CVE-2022-036[18],CVE-2022-0393,CVE-2022-0408,CVE-2022-041[37],CVE-2022-0443, CVE-2022-0554, CVE-2022-0572, CVE-2022-0629, CVE-2022-0685, CVE-2022-0696, CVE-2022-0714 | vim new security issues CVE-2022-0261, CVE-2022-031[89], CVE-2022-035[189],CVE-2022-036[18],CVE-2022-039[23],CVE-2022-040[78],CVE-2022-041[37],CVE-2022-0443,CVE-2022-0554,CVE-2022-0572,CVE-2022-0629,CVE-2022-0685,CVE-2022-0696,CVE-2022-0714,CVE-2022-0729 | ||
| luigiwalser | 2022-11-15 14:57:51 CET | CVE | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019], CVE-2022-1674, CVE-2022-1720, CVE-2022-173[35], CVE-2022-1769, CVE-2022-1771 | CVE-2022-0943, CVE-2022-1154, CVE-2022-1160, CVE-2022-1381, CVE-2022-1420, CVE-2022-161[69], CVE-2022-162[019], CVE-2022-1674, CVE-2022-172[05], CVE-2022-173[35], CVE-2022-1769, CVE-2022-1771 |
Back to bug 29972