| 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.12.0 | n/a | Unknown | CVE-2018-1091 | 3/27/2018 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2018-1091 | 3/27/2018 |
| linux-headers | shell.v0.17.0 | [UNKNOWN] | High | CVE-2018-10901 | 7/26/2018 |
| linux-headers | shell.v0.16.0 | [UNKNOWN] | High | CVE-2018-10901 | 7/26/2018 |
| linux-headers | shell.v0.12.0 | [UNKNOWN] | High | CVE-2018-10901 | 7/26/2018 |
| linux-headers | shell.v0.13.0 | [UNKNOWN] | High | CVE-2018-10901 | 7/26/2018 |
| linux-headers | shell.v0.15.0 | [UNKNOWN] | High | CVE-2018-10901 | 7/26/2018 |
| linux-headers | shell.v0.14.0 | [UNKNOWN] | High | CVE-2018-10901 | 7/26/2018 |
| linux-headers | shell.v0.12.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | shell.v0.13.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | shell.v0.15.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | shell.v0.16.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | shell.v0.17.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | shell.v0.14.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | shell.v0.14.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-headers | shell.v0.12.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-headers | shell.v0.15.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-headers | shell.v0.17.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-headers | shell.v0.13.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-headers | shell.v0.16.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |