| 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.15.0 | Google Inc. | Unknown | CVE-2016-10283 | 5/12/2017 |
| linux-headers | shell.v0.17.0 | Google Inc. | Unknown | CVE-2016-10283 | 5/12/2017 |
| linux-headers | shell.v0.16.0 | Google Inc. | Unknown | CVE-2016-10283 | 5/12/2017 |
| linux-headers | shell.v0.14.0 | Google Inc. | Unknown | CVE-2016-10283 | 5/12/2017 |
| linux-headers | shell.v0.13.0 | Google Inc. | Unknown | CVE-2016-10283 | 5/12/2017 |
| linux-headers | shell.v0.12.0 | Google Inc. | Unknown | CVE-2016-10283 | 5/12/2017 |
| linux-headers | shell.v0.12.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-headers | shell.v0.16.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-headers | shell.v0.17.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-headers | shell.v0.14.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-headers | shell.v0.13.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-headers | shell.v0.15.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2016-10208 | 2/6/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2016-10208 | 2/6/2017 |