NetSight

Security Dashboard

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

Reset
523 matching advisories · page 3 of 18Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2023-2680 This CVE exists because of an incomplete fix for CVE-2021-3750. qemu · qemu, redhat · enterprise_linux 2023-09-13 medium6.5 CVE-2023-3255 A flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. Red Hat · Red Hat Enterprise Linux 8, Red Hat · Red Hat Enterprise Linux 9, qemu · qemu +2 2023-09-13 medium5.5 CVE-2023-42467 QEMU through 8.0.0 could trigger a division by zero in scsi_disk_reset in hw/scsi/scsi-disk.c because scsi_disk_emulate_mode_select does not prevent s->qdev.bl… qemu · qemu 2023-09-11 high8.8 CVE-2020-24165 An issue was discovered in TCG Accelerator in QEMU 4.2.0, allows local attackers to execute arbitrary code, escalate privileges, and cause a denial of service … qemu · qemu, debian · debian_linux 2023-08-28 critical10.0 CVE-2022-36648 The hardware emulation in the of_dpa_cmd_add_l2_flood of rocker device model in QEMU, as used in 7.0.0 and earlier, allows remote attackers to crash the host q… qemu · qemu 2023-08-22 medium5.5 CVE-2023-40360 QEMU through 8.0.4 accesses a NULL pointer in nvme_directive_receive in hw/nvme/ctrl.c because there is no check for whether an endurance group is configured b… qemu · qemu 2023-08-14 medium6.0 CVE-2023-4135 A heap out-of-bounds memory read flaw was found in the virtual nvme device in QEMU. qemu · qemu, fedoraproject · fedora 2023-08-04 medium6.0 CVE-2023-3180 A flaw was found in the QEMU virtual crypto device while handling data encryption/decryption requests in virtio_crypto_handle_sym_req. qemu · qemu, fedoraproject · fedora, debian · debian_linux 2023-08-03 low3.3 CVE-2023-1386 A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. qemu · qemu, fedoraproject · fedora 2023-07-24 medium6.0 CVE-2023-3019 A DMA reentrancy issue leading to a use-after-free error was found in the e1000e NIC emulation code in QEMU. qemu · qemu, redhat · enterprise_linux, Red Hat · Red Hat Enterprise Linux 8.8 Extended Update Support +3 2023-07-24 high7.5 CVE-2023-3354 A flaw was found in the QEMU built-in VNC server. qemu · qemu, redhat · openstack_platform, redhat · enterprise_linux +1 2023-07-11 high7.8 CVE-2023-0664 A flaw was found in the QEMU Guest Agent service for Windows. qemu · qemu, redhat · enterprise_linux, fedoraproject · fedora 2023-03-29 medium6.0 CVE-2023-1544 A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device. qemu · qemu, fedoraproject · fedora 2023-03-23 medium5.3 CVE-2023-0330 A vulnerability in the lsi53c895a device affects the latest version of qemu. qemu · qemu, debian · debian_linux 2023-03-06 medium6.5 CVE-2022-4172 An integer overflow and buffer overflow issues were found in the ACPI Error Record Serialization Table (ERST) device of QEMU in the read_erst_record() and writ… qemu · qemu, fedoraproject · fedora 2022-11-29 medium6.5 CVE-2022-4144 An out-of-bounds read flaw was found in the QXL display device emulation in QEMU. qemu · qemu, fedoraproject · extra_packages_for_enterprise_linux, fedoraproject · fedora +1 2022-11-29 high8.6 CVE-2022-3872 An off-by-one read/write issue was found in the SDHCI device of QEMU. qemu · qemu 2022-11-07 medium6.5 CVE-2022-3165 An integer underflow issue was found in the QEMU VNC server while processing ClientCutText messages in the extended format. qemu · qemu, fedoraproject · fedora 2022-10-17 medium5.5 CVE-2014-0148 Qemu before 2.0 block driver for Hyper-V VHDX Images is vulnerable to infinite loops and other potential issues when calculating BAT entries, due to missing bo… qemu · qemu, redhat · virtualization, redhat · enterprise_linux_desktop +6 2022-09-29 medium6.2 CVE-2014-0147 Qemu before 1.6.2 block diver for the various disk image formats used by Bochs and for the QCOW version 2 format, are vulnerable to a possible crash caused by … qemu · qemu, fedoraproject · fedora, redhat · virtualization +7 2022-09-29 high8.6 CVE-2014-0144 QEMU before 2.0.0 block drivers for CLOOP, QCOW2 version 2 and various other image formats are vulnerable to potential memory corruptions, integer/buffer overf… qemu · qemu, redhat · virtualization, redhat · enterprise_linux_desktop +6 2022-09-29 high7.8 CVE-2022-2962 A DMA reentrancy issue was found in the Tulip device emulation in QEMU. qemu · qemu 2022-09-13 high7.8 CVE-2022-0358 A flaw was found in the QEMU virtio-fs shared file system daemon (virtiofsd) implementation. qemu · qemu, redhat · enterprise_linux 2022-08-29 medium4.4 CVE-2022-0216 A use-after-free vulnerability was found in the LSI53C895A SCSI Host Bus Adapter emulation of QEMU. qemu · qemu, fedoraproject · fedora 2022-08-26 medium4.4 CVE-2021-3735 A deadlock issue was found in the AHCI controller device of QEMU. qemu · qemu, debian · debian_linux 2022-08-26 high8.2 CVE-2021-3929 A DMA reentrancy issue was found in the NVM Express Controller (NVME) emulation in QEMU. qemu · qemu, fedoraproject · fedora 2022-08-25 medium6.0 CVE-2021-4158 A NULL pointer dereference issue was found in the ACPI code of QEMU. qemu · qemu, redhat · enterprise_linux 2022-08-24 low3.2 CVE-2020-14394 An infinite loop flaw was found in the USB xHCI controller emulation of QEMU while computing the length of the Transfer Request Block (TRB) Ring. qemu · qemu, fedoraproject · extra_packages_for_enterprise_linux, fedoraproject · fedora +2 2022-08-17 high8.8 CVE-2022-35414 softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path, leading to an io_readx or io_writex crash. qemu · qemu, debian · debian_linux 2022-07-11 high7.5 CVE-2022-29694 Unicorn Engine v2.0.0-rc7 and below was discovered to contain a NULL pointer dereference via qemu_ram_free. unicorn-engine · unicorn_engine 2022-06-02

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.