| 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.13.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | shell.v0.14.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | shell.v0.17.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | shell.v0.12.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | shell.v0.16.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | shell.v0.15.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | shell.v0.17.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | shell.v0.14.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | shell.v0.16.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | shell.v0.15.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | shell.v0.12.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | shell.v0.13.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | shell.v0.12.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | shell.v0.17.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | shell.v0.13.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | shell.v0.14.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | shell.v0.15.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | shell.v0.16.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | shell.v0.15.0 | n/a | High | CVE-2022-47521 | 12/18/2022 |
| linux-headers | shell.v0.16.0 | n/a | High | CVE-2022-47521 | 12/18/2022 |