| 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.17.0 | n/a | Unknown | CVE-2017-7187 | 3/20/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-7187 | 3/20/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-7184 | 3/19/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-7184 | 3/19/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2017-7184 | 3/19/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2017-7184 | 3/19/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-7184 | 3/19/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-7184 | 3/19/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2017-6951 | 3/16/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-6951 | 3/16/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-6951 | 3/16/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-6951 | 3/16/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2017-6951 | 3/16/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-6951 | 3/16/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-6874 | 3/14/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2017-6874 | 3/14/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-6874 | 3/14/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2017-6874 | 3/14/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-6874 | 3/14/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-6874 | 3/14/2017 |