This page was not yet optimized for use on mobile devices.
CVE-2013-2016
Data ?
Vulnerability ID | CVE-2013-2016 |
---|---|
Published on | 30.12.2019 22:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:qemu:qemu:1.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.3.0:rc0:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.3.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.3.0:rc2:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.4.0:-:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.4.0:rc0:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.4.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:qemu:qemu:1.4.0:rc2:*:*:*:*:*:*,
…
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.