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
2.013
2.112
2.212

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 Fix316
Temporary Fix0
Workaround0
Unavailable1
Not Defined90

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-Concept16
Unproven54
Not Defined337

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
Local221
Adjacent85
Network101

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
High54
Low205
None148

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
None407

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
≤32
≤436
≤585
≤6138
≤763
≤851
≤923
≤109

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
≤32
≤438
≤5101
≤6134
≤763
≤845
≤918
≤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
≤37
≤498
≤536
≤6156
≤735
≤837
≤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
≤415
≤523
≤6106
≤753
≤845
≤921
≤1013

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
≤41
≤53
≤68
≤74
≤83
≤92
≤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
<2k46
<5k126
<10k91
<25k128
<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

<1k310
<2k21
<5k41
<10k27
<25k8
<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 (144): 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+dfsg, 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.0oa, 4.2.0ob, 4.2.0oc, 4.2.0od, 4.2.0oe, 4.2.0of, 4.2.0og, 4.2.0oh, 4.2.0oi, 4.2.0oj, 4.2.0ok, 4.2.0ol, 4.2.0om, 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, 8.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.1, 8.2, 8.2.1, 14.04, 16.04, 18.04, 18.10

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

Software Type: Virtualization Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
05/10/20245.55.5QEMU Virtio PCI Binding virtio-pci.c vhost_net_stop operation after expiration$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2024-4693
04/10/20245.55.5QEMU Fragmented Packet net_tx_pkt.c update_sctp_checksum assertion$0-$5k$0-$5kNot DefinedNot Defined0.08CVE-2024-3567
04/10/20247.47.4QEMU virtio-gpu/virtio-serial-bus/virtio-crypto double free$5k-$25k$5k-$25kNot DefinedNot Defined0.03CVE-2024-3446
04/09/20245.55.3QEMU sdhci_write_dataport heap-based overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-3447
02/20/20246.36.0QEMU pdb.c pdb_get_file_size(const data authenticity$5k-$25k$0-$5kNot DefinedOfficial Fix0.07CVE-2024-24475
02/20/20246.36.0QEMU buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-24474
02/19/20245.55.5QEMU pcie_sriov.c register_vfs Privilege Escalation$5k-$25k$5k-$25kNot DefinedNot Defined0.08CVE-2024-26328
02/19/20245.55.3QEMU pcie_sriov.c register_vfs buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2024-26327
01/12/20246.56.3QEMU Built-In VNC Server qemu_clipboard_request null pointer dereference$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2023-6683
01/02/20245.25.2QEMU virtio-net Device virtio_net_flush_tx stack-based overflow$0-$5k$5k-$25kNot DefinedNot Defined0.04CVE-2023-6693
11/01/20236.05.9QEMU Disk Offset core.c ide_dma_cb memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2023-5088
09/11/20235.65.5QEMU scsi-disk.c scsi_disk_reset divide by zero$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2023-42467
08/29/20237.07.0QEMU TCG Accelerator Local Privilege Escalation$0-$5k$0-$5kNot DefinedNot Defined0.08CVE-2020-24165
08/23/20238.28.2QEMU Rocker Device Model of_dpa_cmd_add_l2_flood denial of service$5k-$25k$0-$5kNot DefinedNot Defined0.06CVE-2022-36648
08/14/20234.54.4QEMU ctrl.c nvme_directive_receive null pointer dereference$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-40360
08/04/20234.94.9QEMU out-of-bounds$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2023-4135
08/03/20236.05.9QEMU Virtual Crypto Device virtio-crypto.c virtio_crypto_sym_op_helper heap-based overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2023-3180
08/01/20232.62.5QEMU Hot-Unplug race condition$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-3301
07/24/20233.93.9QEMU 9pfs Passthrough Filesystem privilege dropping / lowering errors$0-$5k$0-$5kNot DefinedNot Defined0.07CVE-2023-1386
07/12/20235.75.6QEMU e1000e e1000e_write_packet_to_guest use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2023-3019
07/04/20233.53.4QEMU VNC vnc-clipboard.c inflate_buffer denial of service$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-3255
07/03/20235.55.3QEMU 9pfs 9p-util.h openat_dir access control$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2023-2861
06/29/20236.46.4QEMU VNC Server null pointer dereference$5k-$25k$5k-$25kNot DefinedNot Defined0.03CVE-2023-3354
04/22/20236.56.3Fabrice Bellard QEMU CLIENT_CUT_TEXT Message infinite loop$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2015-5239
04/22/20237.87.6QEMU memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2013-4532

382 more entries are not shown

Do you know our Splunk app?

Download it now for free!