NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
291 matching advisories · page 4 of 10Index is being built · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.6 CVE-2020-13765 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 mem… qemu · qemu, canonical · ubuntu_linux, debian · debian_linux 2020-06-04 medium6.7 CVE-2020-13754 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. qemu · qemu, canonical · ubuntu_linux, debian · debian_linux 2020-06-02 medium5.5 CVE-2020-13253 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. qemu · qemu, canonical · ubuntu_linux, debian · debian_linux 2020-05-27 medium6.5 CVE-2020-12430 An issue was discovered in qemuDomainGetStatsIOThread in qemu/qemu_driver.c in libvirt 4.10.0 though 6.x before 6.1.0. redhat · libvirt, redhat · enterprise_linux 2020-04-28 medium5.6 CVE-2020-11102 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. qemu · qemu 2020-04-06 medium5.7 CVE-2019-20485 qemu/qemu_driver.c in libvirt before 6.0.0 mishandles the holding of a monitor job during a query to a guest agent, which allows attackers to cause a denial of… redhat · libvirt, debian · debian_linux, fedoraproject · fedora 2020-03-19 medium5.8 CVE-2019-15034 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 con… qemu · qemu 2020-03-10 medium5.6 CVE-2020-8608 In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code. libslirp_project · libslirp, debian · debian_linux, opensuse · leap 2020-02-06 medium6.5 CVE-2015-5745 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 proc… qemu · qemu, fedoraproject · fedora, arista · eos 2020-01-23 medium6.5 CVE-2015-5278 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 possi… qemu · qemu, fedoraproject · fedora, canonical · ubuntu_linux +1 2020-01-23 medium6.5 CVE-2015-5239 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, wh… qemu · qemu, fedoraproject · fedora, canonical · ubuntu_linux +5 2020-01-23 medium5.6 CVE-2020-7039 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. libslirp_project · libslirp, qemu · qemu, debian · debian_linux +1 2020-01-16 medium5.5 CVE-2019-9824 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. qemu · qemu 2019-06-03 medium5.8 CVE-2019-3840 A NULL pointer dereference flaw was discovered in libvirt before version 5.0.0 in the way it gets interface information through the QEMU agent. redhat · libvirt, opensuse · leap 2019-03-27 medium5.5 CVE-2019-6501 In QEMU 3.1, scsi_handle_inquiry_reply in hw/scsi/scsi-generic.c allows out-of-bounds write and read operations. qemu · qemu, fedoraproject · fedora 2019-03-21 medium5.5 CVE-2018-18849 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. qemu · qemu, opensuse · leap, fedoraproject · fedora +1 2019-03-21 medium4.4 CVE-2019-3812 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. qemu · qemu, fedoraproject · fedora, canonical · ubuntu_linux +1 2019-02-19 medium5.5 CVE-2018-20124 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. qemu · qemu, canonical · ubuntu_linux 2018-12-20 medium5.5 CVE-2018-20126 hw/rdma/vmw/pvrdma_cmd.c in QEMU allows create_cq and create_qp memory leaks because errors are mishandled. qemu · qemu, canonical · ubuntu_linux, opensuse · leap 2018-12-20 medium5.5 CVE-2018-20123 pvrdma_realize in hw/rdma/vmw/pvrdma_main.c in QEMU has a Memory leak after an initialisation error. qemu · qemu, canonical · ubuntu_linux, fedoraproject · fedora 2018-12-17 medium5.3 CVE-2018-16872 A flaw was found in qemu Media Transfer Protocol (MTP). qemu · qemu, debian · debian_linux, fedoraproject · fedora +2 2018-12-13 medium4.7 CVE-2018-19489 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. qemu · qemu, debian · debian_linux, fedoraproject · fedora +2 2018-12-13 medium5.5 CVE-2018-19364 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 outco… qemu · qemu, canonical · ubuntu_linux, debian · debian_linux +2 2018-12-13 medium5.7 CVE-2018-19665 The Bluetooth subsystem in QEMU mishandles negative values for length variables, leading to memory corruption. qemu · qemu, opensuse · leap 2018-12-06 medium5.5 CVE-2018-18954 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. qemu · qemu, canonical · ubuntu_linux, opensuse · leap 2018-11-15 medium5.5 CVE-2018-18438 Qemu has integer overflows because IOReadHandler and its associated functions use a signed integer data type for a size value. qemu · qemu, redhat · enterprise_linux, redhat · openstack 2018-10-19 medium6.5 CVE-2018-10839 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. qemu · qemu, canonical · ubuntu_linux, debian · debian_linux 2018-10-16 medium5.5 CVE-2018-15746 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 … qemu · qemu 2018-08-29 medium5.5 CVE-2015-5160 libvirt before 2.2 includes Ceph credentials on the qemu command line when using RADOS Block Device (aka RBD), which allows local users to obtain sensitive inf… libvirt · libvirt, redhat · virtualization, redhat · enterprise_linux +7 2018-08-20 medium6.5 CVE-2018-10908 It was found that vdsm before version 4.20.37 invokes qemu-img on untrusted inputs without limiting resources. ovirt · vdsm, redhat · virtualization 2018-08-09

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.