Back to bug 30561
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| luigiwalser | 2022-06-17 16:40:38 CEST | Status comment | Fixed upstream in 8.2.5063 | |
| lewyssmith | 2022-06-17 21:37:31 CEST | Assignee | bugsquad | thierry.vignaud |
| luigiwalser | 2022-06-21 23:15:47 CEST | Status comment | Fixed upstream in 8.2.5063 | Fixed upstream in 8.2.5123 |
| Summary | vim new security issue CVE-2022-2000 | vim new security issues CVE-2022-2000, CVE-2022-2124, CVE-2022-2126 | ||
| luigiwalser | 2022-06-25 19:07:11 CEST | Summary | vim new security issues CVE-2022-2000, CVE-2022-2124, CVE-2022-2126 | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-2124, CVE-2022-2126 |
| luigiwalser | 2022-06-30 20:19:25 CEST | Summary | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-2124, CVE-2022-2126 | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231 |
| Status comment | Fixed upstream in 8.2.5123 | Fixed upstream in 8.2.5169 | ||
| luigiwalser | 2022-07-14 19:25:47 CEST | Summary | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231 | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-228[5-9], CVE-2022-2264, CVE-2022-2304 |
| Status comment | Fixed upstream in 8.2.5169 | Fixed upstream in 9.0.0035 | ||
| luigiwalser | 2022-07-22 17:12:03 CEST | Summary | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-228[5-9], CVE-2022-2264, CVE-2022-2304 | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-228[5-9], CVE-2022-2264, CVE-2022-2304, CVE-2022-234[3-5] |
| Status comment | Fixed upstream in 9.0.0035 | Fixed upstream in 9.0.0047 | ||
| luigiwalser | 2022-08-23 18:33:27 CEST | Summary | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-228[5-9], CVE-2022-2264, CVE-2022-2304, CVE-2022-234[3-5] | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-228[5-9], CVE-2022-2264, CVE-2022-2304, CVE-2022-234[3-5],CVE-2022-281[679] |
| Status comment | Fixed upstream in 9.0.0047 | Fixed upstream in 9.0.0213 | ||
| luigiwalser | 2022-09-01 23:23:55 CEST | CVE | CVE-2022-2845, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946 | |
| Status comment | Fixed upstream in 9.0.0213 | Fixed upstream in 9.0.0245 | ||
| luigiwalser | 2022-09-06 21:25:41 CEST | CVE | CVE-2022-2845, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946 | CVE-2022-2845, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-3037 |
| Status comment | Fixed upstream in 9.0.0245 | Fixed upstream in 9.0.0322 | ||
| luigiwalser | 2022-09-09 19:36:59 CEST | Summary | ,CVE-2022-281[679] | |
| CVE | CVE-2022-2845, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-3037 | CVE-2022-2522, CVE-2022-2571, CVE-2022-258[01], CVE-2022-2598, CVE-2022-281[679], CVE-2022-284[59], CVE-2022-2862, CVE-2022-2874, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-3016, CVE-2022-3037 | ||
| Summary | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-228[5-9], CVE-2022-2264, CVE-2022-2304, CVE-2022-234[3-5] | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-2257, CVE-2022-2264, CVE-2022-228[4-9], CVE-2022-2304, CVE-2022-234[3-5] | ||
| luigiwalser | 2022-09-09 19:38:57 CEST | Summary | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2126, CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-2257, CVE-2022-2264, CVE-2022-228[4-9], CVE-2022-2304, CVE-2022-234[3-5] | vim new security issues CVE-2022-2000, CVE-2022-2042, CVE-2022-212[4569], CVE-2022-2175, CVE-2022-218[23], CVE-2022-220[6-8], CVE-2022-2210, CVE-2022-2231, CVE-2022-2257, CVE-2022-2264, CVE-2022-228[4-9], CVE-2022-2304, CVE-2022-234[3-5] |
| luigiwalser | 2022-09-14 23:09:34 CEST | CVE | CVE-2022-2522, CVE-2022-2571, CVE-2022-258[01], CVE-2022-2598, CVE-2022-281[679], CVE-2022-284[59], CVE-2022-2862, CVE-2022-2874, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-3016, CVE-2022-3037 | CVE-2022-2522, CVE-2022-2571, CVE-2022-258[01], CVE-2022-2598, CVE-2022-281[679], CVE-2022-284[59], CVE-2022-2862, CVE-2022-2874, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-298[02], CVE-2022-3016, CVE-2022-3037, CVE-2022-3099 |
| Status comment | Fixed upstream in 9.0.0322 | Fixed upstream in 9.0.0360 | ||
| luigiwalser | 2022-10-14 20:00:34 CEST | Status comment | Fixed upstream in 9.0.0360 | Fixed upstream in 9.0.0614 |
| CVE | CVE-2022-2522, CVE-2022-2571, CVE-2022-258[01], CVE-2022-2598, CVE-2022-281[679], CVE-2022-284[59], CVE-2022-2862, CVE-2022-2874, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-298[02], CVE-2022-3016, CVE-2022-3037, CVE-2022-3099 | CVE-2022-2522, CVE-2022-2571, CVE-2022-258[01], CVE-2022-2598, CVE-2022-281[679], CVE-2022-284[59], CVE-2022-2862, CVE-2022-2874, CVE-2022-2889, CVE-2022-2923, CVE-2022-2946, CVE-2022-298[02], CVE-2022-3016, CVE-2022-3037, CVE-2022-3099, CVE-2022-323[45] | ||
| luigiwalser | 2022-11-07 21:17:39 CET | Status comment | Fixed upstream in 9.0.0614 | Fixed upstream in 9.0.0805 |
| nicolas.salguero | 2022-11-16 12:23:36 CET | CC | nicolas.salguero | |
| Status | NEW | ASSIGNED | ||
| Assignee | thierry.vignaud | qa-bugs | ||
| Status comment | Fixed upstream in 9.0.0805 | |||
| herman.viaene | 2022-11-18 17:03:53 CET | Whiteboard | MGA8-64-OK | |
| CC | herman.viaene | |||
| andrewsfarm | 2022-11-18 17:57:57 CET | Keywords | validated_update | |
| CC | andrewsfarm, sysadmin-bugs | |||
| davidwhodgins | 2022-11-18 22:28:49 CET | CC | davidwhodgins | |
| Keywords | advisory | |||
| bot | 2022-11-18 23:52:01 CET | Resolution | --- | FIXED |
| Status | ASSIGNED | RESOLVED |
Back to bug 30561