| 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 | Unknown | CVE-2017-15537 | 10/17/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-15537 | 10/17/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2017-15306 | 11/6/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-15306 | 11/6/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-15306 | 11/6/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-15306 | 11/6/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2017-15306 | 11/6/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-15306 | 11/6/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2017-15299 | 10/14/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-15299 | 10/14/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-15299 | 10/14/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-15299 | 10/14/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-15299 | 10/14/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2017-15299 | 10/14/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2017-15274 | 10/12/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-15274 | 10/12/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-15274 | 10/12/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-15274 | 10/12/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-15274 | 10/12/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2017-15274 | 10/12/2017 |