Qemu Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

1.7.016
5.014
6.011
2.011
2.111

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix293
Temporary Fix0
Workaround0
Unavailable1
Not Defined83

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept15
Unproven54
Not Defined308

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local211
Adjacent72
Network94

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High52
Low178
None147

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required0
None377

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤433
≤583
≤6124
≤757
≤848
≤921
≤1010

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤31
≤437
≤597
≤6118
≤760
≤841
≤917
≤106

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤35
≤495
≤534
≤6142
≤728
≤835
≤927
≤1011

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤31
≤414
≤523
≤6102
≤745
≤843
≤920
≤1012

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤81
≤90
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k2
<2k58
<5k99
<10k80
<25k124
<50k14
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k254
<2k27
<5k45
<10k34
<25k17
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (122): 0.1, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3, 0.5, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.5.5, 0.6, 0.6.1, 0.7, 0.7.1, 0.7.2, 0.8, 0.8.1, 0.8.2, 0.9, 0.9.1, 0.9.1-5, 0.10, 0.10.1, 0.10.2, 0.10.3, 0.10.4, 0.10.5, 0.10.6, 0.11, 0.11.0-rc, 0.11.0-rc1, 0.11.0-rc2, 0.12, 0.14, 0.15, 0.15.1, 1.0, 1.0.1, 1.1, 1.2, 1.3, 1.3.1, 1.4, 1.4.1, 1.4.2, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.6, 1.6.1, 1.6.2, 1.7, 1.7.1, 1:2.1+dfsg-12+deb8u6, 1:2.1+dfsg-12+deb8u12, 1:2.8+dfsg-6+deb9u8, 1:3.1+dfsg-8+deb10u2, 1:3.1+dfsg-8~deb10u1, 1:4.1-1, 2, 2.0, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 2.10, 2.11, 2.12, 2.12.5, 2.14, 2.14.1, 2.14.2, 3, 3.0, 3.1, 3.1.5, 4, 4.0, 4.1, 4.2, 4.2.0on, 4.3, 4.4, 4.5, 5, 5.0, 5.1, 5.2, 6.0, 6.1, 6.1.0-rc1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 7.0, 8.0, 14.04, 16.04, 18.04, 18.10

Link to Product Website: https://www.qemu.org/

Software Type: Virtualization Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
11/30/20226.56.5QEMU QXL Display Device Emulation qxl_phys2virt out-of-bounds$5k-$25k$5k-$25kNot DefinedNot Defined0.14CVE-2022-4144
11/30/20225.55.3QEMU ERST Device write_erst_record integer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-4172
11/08/20227.17.1QEMU SDHCI Device sdhci_write_dataport off-by-one$5k-$25k$5k-$25kNot DefinedNot Defined0.09CVE-2022-3872
10/18/20226.56.2QEMU VNC Server integer underflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-3165
09/14/20226.76.6QEMU Tulip Device Emulation denial of service$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-2962
08/29/20227.06.9QEMU virtio-fs Shared File System Daemon dropped privileges$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-0358
08/27/20224.74.6QEMU LSI53C895A SCSI Host Bus Adapter Emulation lsi_do_msgout use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2022-0216
08/26/20224.34.3QEMU AHCI Controller Device ahci_reset_port locking$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2021-3735
08/26/20226.86.7QEMU NVM Express Controller Emulation nvme_ctrl_reset use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-3929
08/25/20226.56.2QEMU ACPI null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-4158
07/11/20227.27.1QEMU physmem.c translate_fail uninitialized pointer$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-35414
05/12/20225.75.5QEMU HD Audio Device memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2021-3611
05/03/20225.75.5QEMU USB EHCI Controller Emulation use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2021-3750
04/30/20228.08.0QEMU QXL Display Device Emulation heap-based overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.07CVE-2021-4207
04/30/20228.08.0QEMU QXL Display Device Emulation cursor_alloc heap-based overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2021-4206
03/29/20225.55.3QEMU Guest Driver pvrdma_cmd.c use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-1050
03/26/20225.75.7QEMU Vmware Paravirtual RDMA Device memory corruption$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2021-3582
03/24/20225.75.5QEMU virtio-net Device use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-3748
03/17/20223.53.4QEMU vhost-vsock Device release of resource$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-26354
03/17/20223.53.4QEMU virtio-net Device release of resource$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-26353
03/16/20225.75.2QEMU e1000 NIC Emulator process_tx_desc infinite loop$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-20257
03/04/20225.75.7QEMU ATI VGA Device Emulation ati_2d_blt out-of-bounds write$5k-$25k$5k-$25kNot DefinedNot Defined0.19CVE-2021-3638
02/25/20225.75.5QEMU Paravirtual RDMA Device uninitialized pointer$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-3608
02/25/20225.75.5QEMU Paravirtual RDMA Device null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-3607
02/18/20225.75.5QEMU SCSI device Emulation mode_sense_page off-by-one$5k-$25k$5k-$25kNot DefinedNot Defined0.05CVE-2021-3930

352 more entries are not shown

Do you know our Splunk app?

Download it now for free!