This page was not yet optimized for use on mobile devices.
CVE-2016-1922
Data ?
Vulnerability ID | CVE-2016-1922 |
---|---|
Published on | 29.12.2016 22:59 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:qemu:qemu:-:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.1:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.1.2:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.1.3:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.1.4:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.1.5:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.1.6:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:0.2:*:*:*:*:*:*:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.