NetSight

Security Dashboard

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

Reset
523 matching advisories · page 4 of 18Index updated 5 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2021-3611 A stack overflow vulnerability was found in the Intel HD Audio device (intel-hda) of QEMU. qemu · qemu, redhat · enterprise_linux 2022-05-11 high8.2 CVE-2021-3750 A DMA reentrancy issue was found in the USB EHCI controller emulation of QEMU. qemu · qemu, redhat · enterprise_linux 2022-05-02 high8.2 CVE-2021-4207 A flaw was found in the QXL display device emulation in QEMU. qemu · qemu, redhat · enterprise_linux, debian · debian_linux 2022-04-29 high8.2 CVE-2021-4206 A flaw was found in the QXL display device emulation in QEMU. qemu · qemu, redhat · enterprise_linux, debian · debian_linux 2022-04-29 medium6.5 CVE-2021-20295 It was discovered that the update for the virt:rhel module in the RHSA-2020:4676 (https://access.redhat.com/errata/RHSA-2020:4676) erratum released as part of … qemu · qemu 2022-04-01 high8.8 CVE-2022-1050 A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device. qemu · qemu 2022-03-29 medium6.5 CVE-2021-3582 A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device. qemu · qemu, debian · debian_linux 2022-03-25 high7.5 CVE-2021-3748 A use-after-free vulnerability was found in the virtio-net device of QEMU. qemu · qemu, debian · debian_linux, canonical · ubuntu_linux +3 2022-03-23 low3.2 CVE-2022-26354 A flaw was found in the vhost-vsock device of QEMU. qemu · qemu, debian · debian_linux 2022-03-16 high7.5 CVE-2022-26353 A flaw was found in the virtio-net device of QEMU. qemu · qemu, debian · debian_linux 2022-03-16 medium6.5 CVE-2021-20257 An infinite loop flaw was found in the e1000 NIC emulator of the QEMU. qemu · qemu, fedoraproject · fedora, redhat · openstack_platform +5 2022-03-16 medium6.5 CVE-2021-3638 An out-of-bounds memory access flaw was found in the ATI VGA device emulation of QEMU. qemu · qemu, fedoraproject · fedora 2022-03-03 medium6.0 CVE-2021-3608 A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device in versions prior to 6.1.0. qemu · qemu, debian · debian_linux, fedoraproject · fedora 2022-02-24 medium6.0 CVE-2021-3607 An integer overflow was found in the QEMU implementation of VMWare's paravirtual RDMA device in versions prior to 6.1.0. qemu · qemu, debian · debian_linux, fedoraproject · fedora 2022-02-24 medium5.5 CVE-2021-3947 A stack-buffer-overflow was found in QEMU in the NVME component. qemu · qemu 2022-02-18 medium6.5 CVE-2021-3930 An off-by-one error was found in the SCSI device emulation in QEMU. qemu · qemu, redhat · codeready_linux_builder, redhat · codeready_linux_builder_for_ibm_z_systems +7 2022-02-18 medium6.5 CVE-2021-4145 A NULL pointer dereference issue was found in the block mirror layer of QEMU in versions prior to 6.2.0. qemu · qemu, redhat · enterprise_linux 2022-01-25 medium6.5 CVE-2021-21896 A directory traversal vulnerability exists in the Web Manager FsBrowseClean functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 high7.2 CVE-2021-21895 A directory traversal vulnerability exists in the Web Manager FsTFtp functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 critical9.1 CVE-2021-21894 A directory traversal vulnerability exists in the Web Manager FsTFtp functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 critical9.9 CVE-2021-21892 A stack-based buffer overflow vulnerability exists in the Web Manager FsUnmount functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 critical9.1 CVE-2021-21891 A stack-based buffer overflow vulnerability exists in the Web Manager FsBrowseClean functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 critical9.1 CVE-2021-21890 A stack-based buffer overflow vulnerability exists in the Web Manager FsBrowseClean functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 critical9.9 CVE-2021-21889 A stack-based buffer overflow vulnerability exists in the Web Manager Ping functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 critical9.1 CVE-2021-21888 An OS command injection vulnerability exists in the Web Manager SslGenerateCertificate functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 critical9.1 CVE-2021-21887 A stack-based buffer overflow vulnerability exists in the Web Manager SslGenerateCSR functionality of Lantronix PremierWave 2050 8.9.0.0R4 (in QEMU). lantronix · premierwave_2050_firmware 2021-12-22 high7.4 CVE-2021-3713 An out-of-bounds write flaw was found in the UAS (USB Attached SCSI) device emulation of QEMU in versions prior to 6.2.0-rc0. qemu · qemu, debian · debian_linux 2021-08-25 high8.5 CVE-2021-3682 A flaw was found in the USB redirector device emulation of QEMU in versions prior to 6.1.0-rc2. qemu · qemu, redhat · enterprise_linux, debian · debian_linux 2021-08-05 low3.8 CVE-2021-3595 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 low3.8 CVE-2021-3594 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

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.