| 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.16.0 | n/a | Unknown | CVE-2018-7480 | 2/25/2018 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2018-7480 | 2/25/2018 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2018-7480 | 2/25/2018 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2018-7480 | 2/25/2018 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2018-7480 | 2/25/2018 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2018-7480 | 2/25/2018 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2018-7273 | 2/21/2018 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2018-7273 | 2/21/2018 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2018-7273 | 2/21/2018 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2018-7273 | 2/21/2018 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2018-7273 | 2/21/2018 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2018-7273 | 2/21/2018 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2018-7191 | 5/17/2019 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2018-7191 | 5/17/2019 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2018-7191 | 5/17/2019 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2018-7191 | 5/17/2019 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2018-7191 | 5/17/2019 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2018-7191 | 5/17/2019 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2018-6927 | 2/12/2018 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2018-6927 | 2/12/2018 |