| 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.3 | n/a | Unknown | CVE-2018-15471 | 8/17/2018 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2018-15471 | 8/17/2018 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2018-15471 | 8/17/2018 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2018-15471 | 8/17/2018 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2018-14734 | 7/29/2018 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2018-14734 | 7/29/2018 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2018-14734 | 7/29/2018 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2018-14734 | 7/29/2018 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2018-14734 | 7/29/2018 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2018-14734 | 7/29/2018 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2018-14678 | 7/28/2018 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2018-14678 | 7/28/2018 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2018-14678 | 7/28/2018 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2018-14678 | 7/28/2018 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2018-14678 | 7/28/2018 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2018-14678 | 7/28/2018 |
| linux-headers | vhd-format.0.12.0 | [UNKNOWN] | High | CVE-2018-14656 | 10/8/2018 |
| linux-headers | vhd-format.0.12.2 | [UNKNOWN] | High | CVE-2018-14656 | 10/8/2018 |
| linux-headers | vhd-format.0.9.1 | [UNKNOWN] | High | CVE-2018-14656 | 10/8/2018 |
| linux-headers | vhd-format.0.13.0 | [UNKNOWN] | High | CVE-2018-14656 | 10/8/2018 |