| 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 | [UNKNOWN] | Medium | CVE-2018-10878 | 7/26/2018 |
| linux-headers | shell.v0.17.0 | [UNKNOWN] | Medium | CVE-2018-10878 | 7/26/2018 |
| linux-headers | shell.v0.15.0 | [UNKNOWN] | Medium | CVE-2018-10878 | 7/26/2018 |
| linux-headers | shell.v0.12.0 | [UNKNOWN] | Medium | CVE-2018-10878 | 7/26/2018 |
| linux-headers | shell.v0.12.0 | [UNKNOWN] | High | CVE-2018-10877 | 7/18/2018 |
| linux-headers | shell.v0.13.0 | [UNKNOWN] | High | CVE-2018-10877 | 7/18/2018 |
| linux-headers | shell.v0.16.0 | [UNKNOWN] | High | CVE-2018-10877 | 7/18/2018 |
| linux-headers | shell.v0.17.0 | [UNKNOWN] | High | CVE-2018-10877 | 7/18/2018 |
| linux-headers | shell.v0.14.0 | [UNKNOWN] | High | CVE-2018-10877 | 7/18/2018 |
| linux-headers | shell.v0.15.0 | [UNKNOWN] | High | CVE-2018-10877 | 7/18/2018 |
| linux-headers | shell.v0.12.0 | kernel | High | CVE-2018-1087 | 5/15/2018 |
| linux-headers | shell.v0.13.0 | kernel | High | CVE-2018-1087 | 5/15/2018 |
| linux-headers | shell.v0.17.0 | kernel | High | CVE-2018-1087 | 5/15/2018 |
| linux-headers | shell.v0.14.0 | kernel | High | CVE-2018-1087 | 5/15/2018 |
| linux-headers | shell.v0.15.0 | kernel | High | CVE-2018-1087 | 5/15/2018 |
| linux-headers | shell.v0.16.0 | kernel | High | CVE-2018-1087 | 5/15/2018 |
| linux-headers | shell.v0.16.0 | Linux | High | CVE-2018-10853 | 9/11/2018 |
| linux-headers | shell.v0.17.0 | Linux | High | CVE-2018-10853 | 9/11/2018 |
| linux-headers | shell.v0.14.0 | Linux | High | CVE-2018-10853 | 9/11/2018 |
| linux-headers | shell.v0.12.0 | Linux | High | CVE-2018-10853 | 9/11/2018 |