NetSight

Security Dashboard

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

Reset
523 matching advisories · page 5 of 18Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.8 CVE-2021-3593 An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. libslirp_project · libslirp, redhat · enterprise_linux, fedoraproject · fedora +1 2021-06-15 low3.8 CVE-2021-3592 An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. libslirp_project · libslirp, redhat · enterprise_linux, debian · debian_linux +1 2021-06-15 medium6.5 CVE-2020-27661 A divide-by-zero issue was found in dwc2_handle_packet in hw/usb/hcd-dwc2.c in the hcd-dwc2 USB host controller emulation of QEMU. qemu · qemu 2021-06-02 medium6.5 CVE-2019-12067 The ahci_commit_buf function in ide/ahci.c in QEMU allows attackers to cause a denial of service (NULL dereference) when the command header 'ad->cur_cmd' is nu… qemu · qemu, debian · debian_linux, fedoraproject · fedora +2 2021-06-02 high8.2 CVE-2021-3546 An out-of-bounds write vulnerability was found in the virtio vhost-user GPU device (vhost-user-gpu) of QEMU in versions up to and including 6.0. qemu · qemu, debian · debian_linux 2021-06-02 medium6.5 CVE-2021-3545 An information disclosure vulnerability was found in the virtio vhost-user GPU device (vhost-user-gpu) of QEMU in versions up to and including 6.0. qemu · qemu, debian · debian_linux 2021-06-02 medium6.5 CVE-2021-3544 Several memory leaks were found in the virtio vhost-user GPU device (vhost-user-gpu) of QEMU in versions up to and including 6.0. qemu · qemu, debian · debian_linux 2021-06-02 medium6.0 CVE-2020-35503 A NULL pointer dereference flaw was found in the megasas-gen2 SCSI host bus adapter emulation of QEMU in versions before and including 6.0. qemu · qemu, fedoraproject · fedora 2021-06-02 high7.8 CVE-2013-4536 An user able to alter the savevm data (either on the disk or over the wire during migration) could use this flaw to to corrupt QEMU process memory on the (dest… qemu · qemu 2021-05-28 medium6.7 CVE-2020-35506 A use-after-free vulnerability was found in the am53c974 SCSI host bus adapter emulation of QEMU in versions before 6.0.0 during the handling of the 'Informati… qemu · qemu 2021-05-28 medium4.4 CVE-2020-35505 A NULL pointer dereference flaw was found in the am53c974 SCSI host bus adapter emulation of QEMU in versions before 6.0.0. qemu · qemu, debian · debian_linux 2021-05-28 medium6.0 CVE-2020-35504 A NULL pointer dereference flaw was found in the SCSI emulation support of QEMU in versions before 6.0.0. qemu · qemu, fedoraproject · fedora, debian · debian_linux 2021-05-28 medium6.5 CVE-2020-10701 A missing authorization flaw was found in the libvirt API responsible for changing the QEMU agent response timeout. redhat · libvirt 2021-05-27 medium5.5 CVE-2021-3527 A flaw was found in the USB redirector device (usb-redir) of QEMU. qemu · qemu, redhat · enterprise_linux, debian · debian_linux 2021-05-26 medium6.5 CVE-2021-20196 A NULL pointer dereference flaw was found in the floppy disk emulator of QEMU. qemu · qemu, debian · debian_linux 2021-05-26 medium6.0 CVE-2021-20221 An out-of-bounds heap buffer access issue was found in the ARM Generic Interrupt Controller emulator of QEMU up to and including qemu 4.2.0on aarch64 platform. qemu · qemu, redhat · enterprise_linux, debian · debian_linux 2021-05-13 high7.5 CVE-2021-20181 A race condition flaw was found in the 9pfs server implementation of QEMU up to and including 5.2.0. qemu · qemu, debian · debian_linux 2021-05-13 medium6.1 CVE-2021-3507 A heap buffer overflow was found in the floppy disk emulator of QEMU up to 6.0.0 (including). qemu · qemu, debian · debian_linux, redhat · enterprise_linux 2021-05-06 medium5.7 CVE-2021-3409 The patch for CVE-2020-17380/CVE-2020-25085 was found to be ineffective, thus making QEMU vulnerable to the out-of-bounds read/write access issues previously f… qemu · qemu, redhat · enterprise_linux, fedoraproject · fedora +1 2021-03-23 low3.2 CVE-2021-3392 A use-after-free flaw was found in the MegaRAID emulator of QEMU. qemu · qemu, fedoraproject · fedora, debian · debian_linux 2021-03-23 medium6.0 CVE-2021-3416 A potential stack overflow via infinite loop issue was found in various NIC emulators of QEMU in versions up to and including 5.2.0. qemu · qemu, fedoraproject · fedora, redhat · enterprise_linux +1 2021-03-18 medium5.5 CVE-2021-20255 A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator of QEMU. qemu · qemu, debian · debian_linux 2021-03-09 low3.3 CVE-2021-20263 A flaw was found in the virtio-fs shared file system daemon (virtiofsd) of QEMU. qemu · qemu 2021-03-09 low3.2 CVE-2021-20203 An integer overflow issue was found in the vmxnet3 NIC emulator of the QEMU for versions up to v5.2.0. qemu · qemu, fedoraproject · fedora, debian · debian_linux 2021-02-25 medium6.3 CVE-2020-17380 A heap-based buffer overflow was found in QEMU through 5.0.0 in the SDHCI device emulation support. qemu · qemu, debian · debian_linux 2021-01-30 high8.2 CVE-2020-35517 A flaw was found in qemu. qemu · qemu 2021-01-28 low3.9 CVE-2020-29443 ide_atapi_cmd_reply_end in hw/ide/atapi.c in QEMU 5.1.0 allows out-of-bounds read access because a buffer index is not validated. qemu · qemu, debian · debian_linux 2021-01-26 low3.8 CVE-2020-11947 iscsi_aio_ioctl_cb in block/iscsi.c in QEMU 4.1.0 has a heap-based buffer over-read that may disclose unrelated information from process memory to an attacker. qemu · qemu 2020-12-31 medium6.5 CVE-2019-20808 In QEMU 4.1.0, an out-of-bounds read flaw was found in the ATI VGA implementation. qemu · qemu 2020-12-31 medium6.0 CVE-2020-27821 A flaw was found in the memory management API of QEMU during the initialization of a memory region cache. qemu · qemu, debian · debian_linux 2020-12-08

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.