| 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 | n/a | Unknown | CVE-2016-4578 | 5/23/2016 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2016-4578 | 5/23/2016 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2016-4569 | 5/23/2016 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2016-4569 | 5/23/2016 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2016-4569 | 5/23/2016 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2016-4569 | 5/23/2016 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2016-4569 | 5/23/2016 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2016-4569 | 5/23/2016 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2016-4568 | 5/23/2016 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2016-4568 | 5/23/2016 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2016-4568 | 5/23/2016 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2016-4568 | 5/23/2016 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2016-4568 | 5/23/2016 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2016-4568 | 5/23/2016 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2016-4565 | 5/23/2016 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2016-4565 | 5/23/2016 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2016-4565 | 5/23/2016 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2016-4565 | 5/23/2016 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2016-4565 | 5/23/2016 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2016-4565 | 5/23/2016 |