Overview 419 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 9 public PoC · 0 EPSS ≥ 0.5
419matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
9public PoC2.1%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
419
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
419
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
8
1.9%
Proof of concept only
6
1.4%
Forecast only
0
0.0%
No public exploit
405
96.7%
split by
peak 91 / year
20077
Not applicable7
High5
Low2
not blocked7
Working exploit published1
No public exploit6
20087
Not applicable7
High3
Medium3
Low1
not blocked7
Working exploit published1
No public exploit6
20091
Not applicable1
Critical1
not blocked1
No public exploit1
20101
Not applicable1
High1
not blocked1
No public exploit1
20110
20127
Not applicable7
High4
Medium2
Low1
not blocked7
No public exploit7
20134
Not applicable4
High2
Medium1
Low1
not blocked4
No public exploit4
201436
Not applicable36
High23
Medium10
Low3
not blocked36
No public exploit36
201511
Not applicable11
High6
Medium4
Low1
not blocked11
Working exploit published2
No public exploit9
201691
Not applicable91
Critical3
High10
Medium77
Low1
not blocked91
No public exploit91
201765
Not applicable65
Critical3
High18
Medium44
not blocked65
Working exploit published1
No public exploit64
201838
Not applicable38
Critical6
High15
Medium17
not blocked38
Working exploit published2
No public exploit36
201917
Not applicable17
Critical3
High8
Medium4
Low2
not blocked17
Working exploit published1
No public exploit16
202046
Not applicable46
High4
Medium25
Low17
not blocked46
No public exploit46
202126
Not applicable26
High6
Medium16
Low4
not blocked26
No public exploit26
202232
Not applicable32
High12
Medium18
Low2
not blocked32
Proof of concept only2
No public exploit30
202317
Not applicable17
Critical1
High7
Medium9
not blocked17
Proof of concept only2
No public exploit15
202411
Not applicable11
High3
Medium8
not blocked11
Proof of concept only2
No public exploit9
20252
Not applicable2
Medium2
not blocked2
No public exploit2
2007200920112013201520172019202120232025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-25625 | Medium | 2020-09-25 | Not applicable | No public exploit | hw/usb/hcd-ohci.c in QEMU 5.0.0 has an infinite loop when a TD list has a loop. |
| CVE-2020-25085 | Medium | 2020-09-25 | Not applicable | No public exploit | QEMU 5.0.0 has a heap-based Buffer Overflow in flatview_read_continue in exec.c because hw/sd/sdhci.c mishandles a write operation in the SDHC_BLKSIZE case. |
| CVE-2020-25084 | Low | 2020-09-25 | Not applicable | No public exploit | QEMU 5.0.0 has a use-after-free in hw/usb/hcd-xhci.c because the usb_packet_map return value is not checked. |
| CVE-2020-14364 | Medium | 2020-08-31 | Not applicable | No public exploit | An out-of-bounds read/write access flaw was found in the USB emulator of the QEMU in versions before 5.2.0. This issue occurs while processing USB packets from a guest when USBDevice 'setup_len' exceeds its 'data_buf[4096]' in the do_token_in, do_token_out routines. This flaw allows a guest user to crash the QEMU process, resulting in a denial of service, or the potential execution of arbitrary code with the privileges of the QEMU process on the host. |
| CVE-2020-12829 | Low | 2020-08-31 | Not applicable | No public exploit | In QEMU through 5.0.0, an integer overflow was found in the SM501 display driver implementation. This flaw occurs in the COPY_AREA macro while handling MMIO write operations through the sm501_2d_engine_write() callback. A local attacker could abuse this flaw to crash the QEMU process in sm501_2d_operation() in hw/display/sm501.c on the host, resulting in a denial of service. |
| CVE-2020-14415 | Low | 2020-08-27 | Not applicable | No public exploit | oss_write in audio/ossaudio.c in QEMU before 5.0.0 mishandles a buffer position. |
| CVE-2020-16092 | Low | 2020-08-11 | Not applicable | No public exploit | In QEMU through 5.0.0, an assertion failure can occur in the network packet processing. This issue affects the e1000e and vmxnet3 network devices. A malicious guest user/process could use this flaw to abort the QEMU process on the host, resulting in a denial of service condition in net_tx_pkt_add_raw_fragment in hw/net/net_tx_pkt.c. |
| CVE-2020-15863 | Medium | 2020-07-28 | Not applicable | No public exploit | hw/net/xgmac.c in the XGMAC Ethernet controller in QEMU before 07-20-2020 has a buffer overflow. This occurs during packet transmission and affects the highbank and midway emulated machines. A guest user or process could use this flaw to crash the QEMU process on the host, resulting in a denial of service or potential privileged code execution. This was fixed in commit 5519724a13664b43e225ca05351c60b4468e4555. |
| CVE-2020-15859 | Low | 2020-07-21 | Not applicable | No public exploit | QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address. |
| CVE-2020-15469 | Low | 2020-07-02 | Not applicable | No public exploit | In QEMU 4.2.0, a MemoryRegionOps object may lack read/write callback methods, leading to a NULL pointer dereference. |
| CVE-2020-10761 | Medium | 2020-06-09 | Not applicable | No public exploit | An assertion failure issue was found in the Network Block Device(NBD) Server in all QEMU versions before QEMU 5.0.1. This flaw occurs when an nbd-client sends a spec-compliant request that is near the boundary of maximum permitted request length. A remote nbd-client could use this flaw to crash the qemu-nbd server resulting in a denial of service. |
| CVE-2020-13800 | Medium | 2020-06-04 | Not applicable | No public exploit | ati-vga in hw/display/ati.c in QEMU 4.2.0 allows guest OS users to trigger infinite recursion via a crafted mm_index value during an ati_mm_read or ati_mm_write call. |
| CVE-2020-13791 | Medium | 2020-06-04 | Not applicable | No public exploit | hw/pci/pci.c in QEMU 4.2.0 allows guest OS users to trigger an out-of-bounds access by providing an address near the end of the PCI configuration space. |
| CVE-2020-13765 | Medium | 2020-06-04 | Not applicable | No public exploit | rom_copy() in hw/core/loader.c in QEMU 4.0 and 4.1.0 does not validate the relationship between two addresses, which allows attackers to trigger an invalid memory copy operation. |
| CVE-2020-10702 | Medium | 2020-06-04 | Not applicable | No public exploit | A flaw was found in QEMU in the implementation of the Pointer Authentication (PAuth) support for ARM introduced in version 4.0 and fixed in version 5.0.0. A general failure of the signature generation process caused every PAuth-enforced pointer to be signed with the same signature. A local attacker could obtain the signature of a protected pointer and abuse this flaw to bypass PAuth protection for all programs running on QEMU. |
| CVE-2020-13754 | Medium | 2020-06-02 | Not applicable | No public exploit | hw/pci/msix.c in QEMU 4.2.0 allows guest OS users to trigger an out-of-bounds access via a crafted address in an msi-x mmio operation. |
| CVE-2020-13659 | Low | 2020-06-02 | Not applicable | No public exploit | address_space_map in exec.c in QEMU 4.2.0 can trigger a NULL pointer dereference related to BounceBuffer. |
| CVE-2020-13362 | Low | 2020-05-28 | Not applicable | No public exploit | In QEMU 5.0.0 and earlier, megasas_lookup_frame in hw/scsi/megasas.c has an out-of-bounds read via a crafted reply_queue_head field from a guest OS user. |
| CVE-2020-13361 | Low | 2020-05-28 | Not applicable | No public exploit | In QEMU 5.0.0 and earlier, es1370_transfer_audio in hw/audio/es1370.c does not properly validate the frame count, which allows guest OS users to trigger an out-of-bounds access during an es1370_write() operation. |
| CVE-2020-13253 | Medium | 2020-05-27 | Not applicable | No public exploit | sd_wp_addr in hw/sd/sd.c in QEMU 4.2.0 uses an unvalidated address, which leads to an out-of-bounds read during sdhci_write() operations. A guest OS user can crash the QEMU process. |
| CVE-2020-10717 | Medium | 2020-05-04 | Not applicable | No public exploit | A potential DoS flaw was found in the virtio-fs shared file system daemon (virtiofsd) implementation of the QEMU version >= v5.0. Virtio-fs is meant to share a host file system directory with a guest via virtio-fs device. If the guest opens the maximum number of file descriptors under the shared directory, a denial of service may occur. This flaw allows a guest user/process to cause this denial of service on the host. |
| CVE-2020-11869 | Low | 2020-04-27 | Not applicable | No public exploit | An integer overflow was found in QEMU 4.0.1 through 4.2.0 in the way it implemented ATI VGA emulation. This flaw occurs in the ati_2d_blt() routine in hw/display/ati-2d.c while handling MMIO write operations through the ati_mm_write() callback. A malicious guest could abuse this flaw to crash the QEMU process, resulting in a denial of service. |
| CVE-2020-11102 | Medium | 2020-04-06 | Not applicable | No public exploit | hw/net/tulip.c in QEMU 4.2.0 has a buffer overflow during the copying of tx/rx buffers because the frame size is not validated against the r/w data length. |
| CVE-2019-15034 | Medium | 2020-03-10 | Not applicable | No public exploit | hw/display/bochs-display.c in QEMU 4.0.0 does not ensure a sufficient PCI config space allocation, leading to a buffer overflow involving the PCIe extended config space. |
| CVE-2019-20382 | Low | 2020-03-05 | Not applicable | No public exploit | QEMU 4.1.0 has a memory leak in zrle_compress_data in ui/vnc-enc-zrle.c during a VNC disconnect operation because libz is misused, resulting in a situation where memory allocated in deflateInit2 is not freed in deflateEnd. |
| CVE-2020-1711 | High | 2020-02-11 | Not applicable | No public exploit | An out-of-bounds heap buffer access flaw was found in the way the iSCSI Block driver in QEMU versions 2.12.0 before 4.2.1 handled a response coming from an iSCSI server while checking the status of a Logical Address Block (LBA) in an iscsi_co_block_status() routine. A remote user could use this flaw to crash the QEMU process, resulting in a denial of service or potential execution of arbitrary code with privileges of the QEMU process on the host. |
| CVE-2013-4535 | High | 2020-02-11 | Not applicable | No public exploit | The virtqueue_map_sg function in hw/virtio/virtio.c in QEMU before 1.7.2 allows remote attackers to execute arbitrary files via a crafted savevm image, related to virtio-block or virtio-serial read. |
| CVE-2015-6815 | Low | 2020-01-31 | Not applicable | No public exploit | The process_tx_desc function in hw/net/e1000.c in QEMU before 2.4.0.1 does not properly process transmit descriptor data when sending a network packet, which allows attackers to cause a denial of service (infinite loop and guest crash) via unspecified vectors. |
| CVE-2015-5745 | Medium | 2020-01-23 | Not applicable | No public exploit | Buffer overflow in the send_control_msg function in hw/char/virtio-serial-bus.c in QEMU before 2.4.0 allows guest users to cause a denial of service (QEMU process crash) via a crafted virtio control message. |
| CVE-2015-5278 | Medium | 2020-01-23 | Not applicable | No public exploit | The ne2000_receive function in hw/net/ne2000.c in QEMU before 2.4.0.1 allows attackers to cause a denial of service (infinite loop and instance crash) or possibly execute arbitrary code via vectors related to receiving packets. |
| CVE-2015-5239 | Medium | 2020-01-23 | Not applicable | No public exploit | Integer overflow in the VNC display driver in QEMU before 2.1.0 allows attachers to cause a denial of service (process crash) via a CLIENT_CUT_TEXT message, which triggers an infinite loop. |
| CVE-2020-7211 | High | 2020-01-21 | Not applicable | No public exploit | tftp.c in libslirp 4.1.0, as used in QEMU 4.2.0, does not prevent ..\ directory traversal on Windows. |
| CVE-2020-7039 | Medium | 2020-01-16 | Not applicable | No public exploit | tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code. |
| CVE-2013-4532 | High | 2020-01-02 | Not applicable | No public exploit | Qemu 1.1.2+dfsg to 2.1+dfsg suffers from a buffer overrun which could potentially result in arbitrary code execution on the host with the privileges of the QEMU process. |
| CVE-2019-20175 | High | 2019-12-31 | Not applicable | No public exploit | An issue was discovered in ide_dma_cb() in hw/ide/core.c in QEMU 2.4.0 through 4.2.0. The guest system can crash the QEMU process in the host system via a special SCSI_IOCTL_SEND_COMMAND. It hits an assertion that implies that the size of successful DMA transfers there must be a multiple of 512 (the size of a sector). NOTE: a member of the QEMU security team disputes the significance of this issue because a "privileged guest user has many ways to cause similar DoS effect, without triggering this assert. |
| CVE-2013-2016 | High | 2019-12-30 | Not applicable | No public exploit | A flaw was found in the way qemu v1.3.0 and later (virtio-rng) validates addresses when guest accesses the config space of a virtio device. If the virtio device has zero/small sized config space, such as virtio-rng, a privileged guest user could use this flaw to access the matching host's qemu address space and thus increase their privileges on the host. |
| CVE-2019-12068 | Low | 2019-09-24 | Not applicable | No public exploit | In QEMU 1:4.1-1, 1:2.1+dfsg-12+deb8u6, 1:2.8+dfsg-6+deb9u8, 1:3.1+dfsg-8~deb10u1, 1:3.1+dfsg-8+deb10u2, and 1:2.1+dfsg-12+deb8u12 (fixed), when executing script in lsi_execute_script(), the LSI scsi adapter emulator advances 's->dsp' index to read next opcode. This can lead to an infinite loop if the next opcode is empty. Move the existing loop exit after 10k iterations so that it covers no-op opcodes as well. |
| CVE-2019-15890 | High | 2019-09-06 | Not applicable | No public exploit | libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c. |
| CVE-2019-13164 | High | 2019-07-03 | Not applicable | No public exploit | qemu-bridge-helper.c in QEMU 3.1 and 4.0.0 does not ensure that a network interface name (obtained from bridge.conf or a --br=bridge option) is limited to the IFNAMSIZ size, which can lead to an ACL bypass. |
| CVE-2019-12929 | Critical | 2019-06-24 | Not applicable | No public exploit | The QMP guest_exec command in QEMU 4.0.0 and earlier is prone to OS command injection, which allows the attacker to achieve code execution, denial of service, or information disclosure by sending a crafted QMP command to the listening server. Note: This has been disputed as a non-issue since QEMU's -qmp interface is meant to be used by trusted users. If one is able to access this interface via a tcp socket open to the internet, then it is an insecure configuration issue |
| CVE-2019-12928 | Critical | 2019-06-24 | Not applicable | Working exploit published | The QMP migrate command in QEMU version 4.0.0 and earlier is vulnerable to OS command injection, which allows the remote attacker to achieve code execution, denial of service, or information disclosure by sending a crafted QMP command to the listening server. Note: This has been disputed as a non-issue since QEMU's -qmp interface is meant to be used by trusted users. If one is able to access this interface via a tcp socket open to the internet, then it is an insecure configuration issue |
| CVE-2019-9824 | Medium | 2019-06-03 | Not applicable | No public exploit | tcp_emu in slirp/tcp_subr.c (aka slirp/src/tcp_subr.c) in QEMU 3.0.0 uses uninitialized data in an snprintf call, leading to Information disclosure. |
| CVE-2018-20815 | Critical | 2019-05-31 | Not applicable | No public exploit | In QEMU 3.1.0, load_device_tree in device_tree.c calls the deprecated load_image function, which has a buffer overflow risk. |
| CVE-2019-12155 | High | 2019-05-24 | Not applicable | No public exploit | interface_release_resource in hw/display/qxl.c in QEMU 3.1.x through 4.0.0 has a NULL pointer dereference. |
| CVE-2019-12247 | High | 2019-05-22 | Not applicable | No public exploit | QEMU 3.0.0 has an Integer Overflow because the qga/commands*.c files do not check the length of the argument list or the number of environment variables. NOTE: This has been disputed as not exploitable |
| CVE-2019-5008 | High | 2019-04-19 | Not applicable | No public exploit | hw/sparc64/sun4u.c in QEMU 3.1.50 is vulnerable to a NULL pointer dereference, which allows the attacker to cause a denial of service via a device driver. |
| CVE-2019-8934 | Low | 2019-03-21 | Not applicable | No public exploit | hw/ppc/spapr.c in QEMU through 3.1.0 allows Information Exposure because the hypervisor shares the /proc/device-tree/system-id and /proc/device-tree/model system attributes with a guest. |
| CVE-2019-6778 | High | 2019-03-21 | Not applicable | No public exploit | In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow. |
| CVE-2019-6501 | Medium | 2019-03-21 | Not applicable | No public exploit | In QEMU 3.1, scsi_handle_inquiry_reply in hw/scsi/scsi-generic.c allows out-of-bounds write and read operations. |
| CVE-2018-18849 | Medium | 2019-03-21 | Not applicable | No public exploit | In Qemu 3.0.0, lsi_do_msgin in hw/scsi/lsi53c895a.c allows out-of-bounds access by triggering an invalid msg_len value. |
| CVE-2019-3812 | Medium | 2019-02-19 | Not applicable | No public exploit | QEMU, through version 2.10 and through version 3.1.0, is vulnerable to an out-of-bounds read of up to 128 bytes in the hw/i2c/i2c-ddc.c:i2c_ddc() function. A local attacker with permission to execute i2c commands could exploit this to read stack memory of the qemu process on the host. |
| CVE-2018-20216 | High | 2018-12-20 | Not applicable | No public exploit | QEMU can have an infinite loop in hw/rdma/vmw/pvrdma_dev_ring.c because return values are not checked (and -1 is mishandled). |
| CVE-2018-20191 | High | 2018-12-20 | Not applicable | No public exploit | hw/rdma/vmw/pvrdma_main.c in QEMU does not implement a read operation (such as uar_read by analogy to uar_write), which allows attackers to cause a denial of service (NULL pointer dereference). |
| CVE-2018-20126 | Medium | 2018-12-20 | Not applicable | No public exploit | hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled. |
| CVE-2018-20125 | High | 2018-12-20 | Not applicable | No public exploit | hw/rdma/vmw/pvrdma_cmd.c in QEMU allows attackers to cause a denial of service (NULL pointer dereference or excessive memory allocation) in create_cq_ring or create_qp_rings. |
| CVE-2018-20124 | Medium | 2018-12-20 | Not applicable | No public exploit | hw/rdma/rdma_backend.c in QEMU allows guest OS users to trigger out-of-bounds access via a PvrdmaSqWqe ring element with a large num_sge value. |
| CVE-2018-20123 | Medium | 2018-12-17 | Not applicable | No public exploit | pvrdma_realize in hw/rdma/vmw/pvrdma_main.c in QEMU has a Memory leak after an initialisation error. |
| CVE-2018-19489 | Medium | 2018-12-13 | Not applicable | No public exploit | v9fs_wstat in hw/9pfs/9p.c in QEMU allows guest OS users to cause a denial of service (crash) because of a race condition during file renaming. |
| CVE-2018-19364 | Medium | 2018-12-13 | Not applicable | No public exploit | hw/9pfs/cofile.c and hw/9pfs/9p.c in QEMU can modify an fid path while it is being accessed by a second thread, leading to (for example) a use-after-free outcome. |
| CVE-2018-16872 | Medium | 2018-12-13 | Not applicable | No public exploit | A flaw was found in qemu Media Transfer Protocol (MTP). The code opening files in usb_mtp_get_object and usb_mtp_get_partial_object and directories in usb_mtp_object_readdir doesn't consider that the underlying filesystem may have changed since the time lstat(2) was called in usb_mtp_object_alloc, a classical TOCTTOU problem. An attacker with write access to the host filesystem shared with a guest can use this property to navigate the host filesystem in the context of the QEMU process and read any file the QEMU process has access to. Access to the filesystem may be local or via a network share protocol such as CIFS. |
| CVE-2018-16867 | High | 2018-12-12 | Not applicable | No public exploit | A flaw was found in qemu Media Transfer Protocol (MTP) before version 3.1.0. A path traversal in the in usb_mtp_write_data function in hw/usb/dev-mtp.c due to an improper filename sanitization. When the guest device is mounted in read-write mode, this allows to read/write arbitrary files which may lead do DoS scenario OR possibly lead to code execution on the host. |
| CVE-2018-19665 | Medium | 2018-12-06 | Not applicable | No public exploit | The Bluetooth subsystem in QEMU mishandles negative values for length variables, leading to memory corruption. |
| CVE-2018-18954 | Medium | 2018-11-15 | Not applicable | No public exploit | The pnv_lpc_do_eccb function in hw/ppc/pnv_lpc.c in Qemu before 3.1 allows out-of-bounds write or read access to PowerNV memory. |
| CVE-2018-16847 | High | 2018-11-02 | Not applicable | No public exploit | An OOB heap buffer r/w access issue was found in the NVM Express Controller emulation in QEMU. It could occur in nvme_cmb_ops routines in nvme device. A guest user/process could use this flaw to crash the QEMU process resulting in DoS or potentially run arbitrary code with privileges of the QEMU process. |
| CVE-2018-18438 | Medium | 2018-10-19 | Not applicable | No public exploit | Qemu has integer overflows because IOReadHandler and its associated functions use a signed integer data type for a size value. |
| CVE-2018-10839 | Medium | 2018-10-16 | Not applicable | No public exploit | Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS. |
| CVE-2018-17963 | Critical | 2018-10-09 | Not applicable | No public exploit | qemu_deliver_packet_iov in net/net.c in Qemu accepts packet sizes greater than INT_MAX, which allows attackers to cause a denial of service or possibly have unspecified other impact. |
| CVE-2018-17962 | High | 2018-10-09 | Not applicable | No public exploit | Qemu has a Buffer Overflow in pcnet_receive in hw/net/pcnet.c because an incorrect integer data type is used. |
| CVE-2018-17958 | High | 2018-10-09 | Not applicable | No public exploit | Qemu has a Buffer Overflow in rtl8139_do_receive in hw/net/rtl8139.c because an incorrect integer data type is used. |
| CVE-2018-15746 | Medium | 2018-08-29 | Not applicable | No public exploit | qemu-seccomp.c in QEMU might allow local OS guest users to cause a denial of service (guest crash) by leveraging mishandling of the seccomp policy for threads other than the main thread. |
| CVE-2017-2633 | Medium | 2018-07-27 | Not applicable | No public exploit | An out-of-bounds memory access issue was found in Quick Emulator (QEMU) before 1.7.2 in the VNC display driver. This flaw could occur while refreshing the VNC display surface area in the 'vnc_refresh_server_surface'. A user inside a guest could use this flaw to crash the QEMU process. |
| CVE-2017-2630 | High | 2018-07-27 | Not applicable | No public exploit | A stack buffer overflow flaw was found in the Quick Emulator (QEMU) before 2.9 built with the Network Block Device (NBD) client support. The flaw could occur while processing server's response to a 'NBD_OPT_LIST' request. A malicious NBD server could use this issue to crash a remote NBD client resulting in DoS or potentially execute arbitrary code on client host with privileges of the QEMU process. |
| CVE-2017-2620 | Critical | 2018-07-27 | Not applicable | No public exploit | Quick emulator (QEMU) before 2.8 built with the Cirrus CLGD 54xx VGA Emulator support is vulnerable to an out-of-bounds access issue. The issue could occur while copying VGA data in cirrus_bitblt_cputovideo. A privileged user inside guest could use this flaw to crash the QEMU process OR potentially execute arbitrary code on host with privileges of the QEMU process. |
| CVE-2017-15119 | High | 2018-07-27 | Not applicable | No public exploit | The Network Block Device (NBD) server in Quick Emulator (QEMU) before 2.11 is vulnerable to a denial of service issue. It could occur if a client sent large option requests, making the server waste CPU time on reading up to 4GB per request. A client could use this flaw to keep the NBD server from serving other requests, resulting in DoS. |
| CVE-2017-15118 | Critical | 2018-07-27 | Not applicable | Working exploit published | A stack-based buffer overflow vulnerability was found in NBD server implementation in qemu before 2.11 allowing a client to request an export name of size up to 4096 bytes, which in fact should be limited to 256 bytes, causing an out-of-bounds stack write in the qemu process. If NBD server requires TLS, the attacker cannot trigger the buffer overflow without first successfully negotiating TLS. |
| CVE-2016-9603 | Critical | 2018-07-27 | Not applicable | No public exploit | A heap buffer overflow flaw was found in QEMU's Cirrus CLGD 54xx VGA emulator's VNC display driver support before 2.9; the issue could occur when a VNC client attempted to update its display after a VGA operation is performed by a guest. A privileged user/process inside a guest could use this flaw to crash the QEMU process or, potentially, execute arbitrary code on the host with privileges of the QEMU process. |
| CVE-2017-7539 | High | 2018-07-26 | Not applicable | No public exploit | An assertion-failure flaw was found in Qemu before 2.10.1, in the Network Block Device (NBD) server's initial connection negotiation, where the I/O coroutine was undefined. This could crash the qemu-nbd server if a client sent unexpected data during connection negotiation. A remote user or process could use this flaw to crash the qemu-nbd server resulting in denial of service. |
| CVE-2017-7471 | Critical | 2018-07-09 | Not applicable | No public exploit | Quick Emulator (Qemu) built with the VirtFS, host directory sharing via Plan 9 File System (9pfs) support, is vulnerable to an improper access control issue. It could occur while accessing files on a shared host directory. A privileged user inside guest could use this flaw to access host file system beyond the shared folder and potentially escalating their privileges on a host. |
| CVE-2017-2615 | Critical | 2018-07-03 | Not applicable | No public exploit | Quick emulator (QEMU) built with the Cirrus CLGD 54xx VGA emulator support is vulnerable to an out-of-bounds access issue. It could occur while copying VGA data via bitblt copy in backward mode. A privileged user inside a guest could use this flaw to crash the QEMU process resulting in DoS or potentially execute arbitrary code on the host with privileges of QEMU process on the host. |
| CVE-2018-12617 | High | 2018-06-21 | Not applicable | Working exploit published | qmp_guest_file_read in qga/commands-posix.c and qga/commands-win32.c in qemu-ga (aka QEMU Guest Agent) in QEMU 2.12.50 has an integer overflow causing a g_malloc0() call to trigger a segmentation fault when trying to allocate a large memory chunk. The vulnerability can be exploited by sending a crafted QMP command (including guest-file-read with a large count value) to the agent via the listening socket. |
| CVE-2018-11806 | High | 2018-06-13 | Not applicable | No public exploit | m_cat in slirp/mbuf.c in Qemu has a heap-based buffer overflow via incoming fragmented datagrams. |
| CVE-2016-9602 | High | 2018-04-26 | Not applicable | No public exploit | Qemu before version 2.9 is vulnerable to an improper link following when built with the VirtFS. A privileged user inside guest could use this flaw to access host file system beyond the shared folder and potentially escalating their privileges on a host. |
| CVE-2018-7858 | Medium | 2018-03-12 | Not applicable | No public exploit | Quick Emulator (aka QEMU), when built with the Cirrus CLGD 54xx VGA Emulator support, allows local guest OS privileged users to cause a denial of service (out-of-bounds access and QEMU process crash) by leveraging incorrect region calculation when updating VGA display. |
| CVE-2018-7550 | High | 2018-03-01 | Not applicable | No public exploit | The load_multiboot function in hw/i386/multiboot.c in Quick Emulator (aka QEMU) allows local guest OS users to execute arbitrary code on the QEMU host via a mh_load_end_addr value greater than mh_bss_end_addr, which triggers an out-of-bounds read or write memory access. |
| CVE-2017-18043 | Medium | 2018-01-31 | Not applicable | No public exploit | Integer overflow in the macro ROUND_UP (n, d) in Quick Emulator (Qemu) allows a user to cause a denial of service (Qemu process crash). |
| CVE-2018-5683 | Medium | 2018-01-23 | Not applicable | No public exploit | The vga_draw_text function in Qemu allows local OS guest privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) by leveraging improper memory address validation. |
| CVE-2017-18030 | Medium | 2018-01-23 | Not applicable | No public exploit | The cirrus_invalidate_region function in hw/display/cirrus_vga.c in Qemu allows local OS guest privileged users to cause a denial of service (out-of-bounds array access and QEMU process crash) via vectors related to negative pitch. |
| CVE-2014-3471 | Medium | 2018-01-12 | Not applicable | No public exploit | Use-after-free vulnerability in hw/pci/pcie.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (QEMU instance crash) via hotplug and hotunplug operations of Virtio block devices. |
| CVE-2017-15124 | High | 2018-01-09 | Not applicable | No public exploit | VNC server implementation in Quick Emulator (QEMU) 2.11.0 and older was found to be vulnerable to an unbounded memory allocation issue, as it did not throttle the framebuffer updates sent to its client. If the client did not consume these updates, VNC server allocates growing memory to hold onto this data. A malicious remote VNC client could use this flaw to cause DoS to the server host. |
| CVE-2017-17381 | Medium | 2017-12-07 | Not applicable | No public exploit | The Virtio Vring implementation in QEMU allows local OS guest users to cause a denial of service (divide-by-zero error and QEMU process crash) by unsetting vring alignment while updating Virtio rings. |
| CVE-2017-16845 | Critical | 2017-11-17 | Not applicable | No public exploit | hw/input/ps2.c in Qemu does not validate 'rptr' and 'count' values during guest migration, leading to out-of-bounds access. |
| CVE-2015-7549 | Medium | 2017-10-30 | Not applicable | No public exploit | The MSI-X MMIO support in hw/pci/msix.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (NULL pointer dereference and QEMU process crash) by leveraging failure to define the .write method. |
| CVE-2017-15289 | Medium | 2017-10-16 | Not applicable | No public exploit | The mode4and5 write functions in hw/display/cirrus_vga.c in Qemu allow local OS guest privileged users to cause a denial of service (out-of-bounds write access and Qemu process crash) via vectors related to dst calculation. |
| CVE-2015-7504 | High | 2017-10-16 | Not applicable | No public exploit | Heap-based buffer overflow in the pcnet_receive function in hw/net/pcnet.c in QEMU allows guest OS administrators to cause a denial of service (instance crash) or possibly execute arbitrary code via a series of packets in loopback mode. |
| CVE-2017-15268 | High | 2017-10-12 | Not applicable | No public exploit | Qemu through 2.10.0 allows remote attackers to cause a memory leak by triggering slow data-channel read operations, related to io/channel-websock.c. |
| CVE-2017-15038 | Medium | 2017-10-10 | Not applicable | No public exploit | Race condition in the v9fs_xattrwalk function in hw/9pfs/9p.c in QEMU (aka Quick Emulator) allows local guest OS users to obtain sensitive information from host heap memory via vectors related to reading extended attributes. |
| CVE-2017-14167 | High | 2017-09-08 | Not applicable | No public exploit | Integer overflow in the load_multiboot function in hw/i386/multiboot.c in QEMU (aka Quick Emulator) allows local guest OS users to execute arbitrary code on the host via crafted multiboot header address values, which trigger an out-of-bounds write. |
| CVE-2017-13711 | High | 2017-09-01 | Not applicable | No public exploit | Use-after-free vulnerability in the sofree function in slirp/socket.c in QEMU (aka Quick Emulator) allows attackers to cause a denial of service (QEMU instance crash) by leveraging failure to properly clear ifq_so from pending packets. |
| CVE-2017-13672 | Medium | 2017-09-01 | Not applicable | No public exploit | QEMU (aka Quick Emulator), when built with the VGA display emulator support, allows local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors involving display update. |
| CVE-2017-13673 | Medium | 2017-08-29 | Not applicable | No public exploit | The vga display update in mis-calculated the region for the dirty bitmap snapshot in case split screen mode is used causing a denial of service (assertion failure) in the cpu_physical_memory_snapshot_get_dirty function. |