This page was not yet optimized for use on mobile devices.
CVE-2020-7211
Data ?
Vulnerability ID | CVE-2020-7211 |
---|---|
Published on | 21.01.2020 17:15 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:qemu:qemu:4.2.0:*:*:*:*:*:*:*, cpe:2.3:a:qemu:qemu:4.2.0:-:*:*:*:*:*:*, cpe:2.3:a:qemu:qemu:4.2.0:rc0:*:*:*:*:*:*, cpe:2.3:a:qemu:qemu:4.2.0:rc1:*:*:*:*:*:*, cpe:2.3:a:qemu:qemu:4.2.0:rc2:*:*:*:*:*:*, cpe:2.3:a:qemu:qemu:4.2.0:rc3:*:*:*:*:*:*, cpe:2.3:a:qemu:qemu:4.2.0:rc4:*:*:*:*:*:*, cpe:2.3:a:qemu:qemu:4.2.0:rc5:*:*:*:*:*:*
-
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*,
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:x64:*,
…
running on/with
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.