| Version | |
|---|---|
| shell.v0.17.0 (latest) | |
| shell.v0.16.0 | |
| shell.v0.15.0 | |
| shell.v0.14.0 | |
| shell.v0.13.0 | |
| shell.v0.12.0 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | shell.v0.14.0 | n/a | High | CVE-2022-4379 | 1/10/2023 |
| linux-headers | shell.v0.15.0 | n/a | High | CVE-2022-4379 | 1/10/2023 |
| linux-headers | shell.v0.16.0 | n/a | High | CVE-2022-4379 | 1/10/2023 |
| linux-headers | shell.v0.17.0 | n/a | High | CVE-2022-4379 | 1/10/2023 |
| linux-headers | shell.v0.16.0 | n/a | High | CVE-2022-4378 | 1/5/2023 |
| linux-headers | shell.v0.13.0 | n/a | High | CVE-2022-4378 | 1/5/2023 |
| linux-headers | shell.v0.12.0 | n/a | High | CVE-2022-4378 | 1/5/2023 |
| linux-headers | shell.v0.14.0 | n/a | High | CVE-2022-4378 | 1/5/2023 |
| linux-headers | shell.v0.15.0 | n/a | High | CVE-2022-4378 | 1/5/2023 |
| linux-headers | shell.v0.17.0 | n/a | High | CVE-2022-4378 | 1/5/2023 |
| linux-headers | shell.v0.15.0 | n/a | Medium | CVE-2022-43750 | 10/26/2022 |
| linux-headers | shell.v0.12.0 | n/a | Medium | CVE-2022-43750 | 10/26/2022 |
| linux-headers | shell.v0.13.0 | n/a | Medium | CVE-2022-43750 | 10/26/2022 |
| linux-headers | shell.v0.14.0 | n/a | Medium | CVE-2022-43750 | 10/26/2022 |
| linux-headers | shell.v0.17.0 | n/a | Medium | CVE-2022-43750 | 10/26/2022 |
| linux-headers | shell.v0.16.0 | n/a | Medium | CVE-2022-43750 | 10/26/2022 |
| linux-headers | shell.v0.16.0 | Linux | High | CVE-2022-42896 - Info Leak in l2cap_core in the Linux Kernel | 11/23/2022 |
| linux-headers | shell.v0.17.0 | Linux | High | CVE-2022-42896 - Info Leak in l2cap_core in the Linux Kernel | 11/23/2022 |
| linux-headers | shell.v0.15.0 | Linux | High | CVE-2022-42896 - Info Leak in l2cap_core in the Linux Kernel | 11/23/2022 |
| linux-headers | shell.v0.13.0 | Linux | High | CVE-2022-42896 - Info Leak in l2cap_core in the Linux Kernel | 11/23/2022 |