| Version | |
|---|---|
| vhd-format.0.9.1 (latest) | |
| vhd-format.0.13.0 | |
| vhd-format.0.12.3 | |
| vhd-format.0.12.2 | |
| vhd-format.0.12.1 | |
| vhd-format.0.12.0 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2017-2671 | 4/5/2017 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2017-2671 | 4/5/2017 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2017-2671 | 4/5/2017 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2017-2671 | 4/5/2017 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| linux-headers | vhd-format.0.9.1 | Linux | High | CVE-2017-2634 | 7/27/2018 |
| linux-headers | vhd-format.0.12.0 | Linux | High | CVE-2017-2634 | 7/27/2018 |
| linux-headers | vhd-format.0.12.3 | Linux | High | CVE-2017-2634 | 7/27/2018 |
| linux-headers | vhd-format.0.13.0 | Linux | High | CVE-2017-2634 | 7/27/2018 |