| 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-2017-2671 | 4/5/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-2671 | 4/5/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-2671 | 4/5/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-2671 | 4/5/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | shell.v0.12.0 | Linux | High | CVE-2017-2634 | 7/27/2018 |
| linux-headers | shell.v0.14.0 | Linux | High | CVE-2017-2634 | 7/27/2018 |
| linux-headers | shell.v0.13.0 | Linux | High | CVE-2017-2634 | 7/27/2018 |
| linux-headers | shell.v0.17.0 | Linux | High | CVE-2017-2634 | 7/27/2018 |