NetSight

Security Dashboard

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

Reset
1,364 matching advisories · page 9 of 46Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2020-2760 Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). oracle · mysql, opensuse · leap, fedoraproject · fedora +6 2020-04-15 medium5.3 CVE-2020-2752 Vulnerability in the MySQL Client product of Oracle MySQL (component: C API). oracle · mysql, mariadb · mariadb, fedoraproject · fedora +5 2020-04-15 medium6.0 CVE-2020-2743 Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). oracle · vm_virtualbox, opensuse · leap 2020-04-15 medium6.0 CVE-2020-2741 Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). oracle · vm_virtualbox, opensuse · leap 2020-04-15 medium5.5 CVE-2020-11765 An issue was discovered in OpenEXR before 2.4.1. openexr · openexr, fedoraproject · fedora, opensuse · leap +9 2020-04-14 medium5.5 CVE-2020-11764 An issue was discovered in OpenEXR before 2.4.1. openexr · openexr, fedoraproject · fedora, canonical · ubuntu_linux +9 2020-04-14 medium5.5 CVE-2020-11763 An issue was discovered in OpenEXR before 2.4.1. openexr · openexr, fedoraproject · fedora, canonical · ubuntu_linux +9 2020-04-14 medium5.5 CVE-2020-11762 An issue was discovered in OpenEXR before 2.4.1. openexr · openexr, fedoraproject · fedora, canonical · ubuntu_linux +9 2020-04-14 medium5.5 CVE-2020-11760 An issue was discovered in OpenEXR before 2.4.1. openexr · openexr, fedoraproject · fedora, canonical · ubuntu_linux +9 2020-04-14 medium5.5 CVE-2020-11758 An issue was discovered in OpenEXR before 2.4.1. openexr · openexr, fedoraproject · fedora, canonical · ubuntu_linux +9 2020-04-14 medium5.5 CVE-2020-11740 An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (without active profiling) to obtain sensitive information about other guest… xen · xen, debian · debian_linux, fedoraproject · fedora +1 2020-04-14 medium6.5 CVE-2020-6456 Insufficient validation of untrusted input in clipboard in Google Chrome prior to 81.0.4044.92 allowed a local attacker to bypass site isolation via crafted cl… google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium6.5 CVE-2020-6446 Insufficient policy enforcement in trusted types in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to bypass content security policy via a craft… google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium6.5 CVE-2020-6445 Insufficient policy enforcement in trusted types in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to bypass content security policy via a craft… google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium6.3 CVE-2020-6444 Uninitialized use in WebRTC in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. google · chrome, fedoraproject · fedora, debian · debian_linux +2 2020-04-13 medium4.3 CVE-2020-6442 Inappropriate implementation in cache in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to leak cross-origin data via a crafted HTML page. google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium4.3 CVE-2020-6441 Insufficient policy enforcement in omnibox in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to bypass security UI via a crafted HTML page. google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium4.3 CVE-2020-6440 Inappropriate implementation in extensions in Google Chrome prior to 81.0.4044.92 allowed an attacker who convinced a user to install a malicious extension to … google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium4.3 CVE-2020-6438 Insufficient policy enforcement in extensions in Google Chrome prior to 81.0.4044.92 allowed an attacker who convinced a user to install a malicious extension … google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium4.3 CVE-2020-6437 Inappropriate implementation in WebView in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to spoof security UI via a crafted application. google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium4.3 CVE-2020-6435 Insufficient policy enforcement in extensions in Google Chrome prior to 81.0.4044.92 allowed a remote attacker who had compromised the renderer process to bypa… google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium4.3 CVE-2020-6433 Insufficient policy enforcement in extensions in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to bypass navigation restrictions via a crafted … google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium4.3 CVE-2020-6432 Insufficient policy enforcement in navigations in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to bypass navigation restrictions via a crafted… google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium4.3 CVE-2020-6431 Insufficient policy enforcement in full screen in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to spoof security UI via a crafted HTML page. google · chrome, debian · debian_linux, fedoraproject · fedora +2 2020-04-13 medium5.5 CVE-2020-11669 An issue was discovered in the Linux kernel before 5.2 on the powerpc platform. linux · linux_kernel, opensuse · leap, redhat · enterprise_linux 2020-04-10 medium6.5 CVE-2020-8834 KVM in the Linux kernel on Power8 processors has a conflicting use of HSTATE_HOST_R1 to store r1 state in kvmppc_hv_entry plus in kvmppc_{save,restore}_tm, lea… linux · linux_kernel, canonical · ubuntu_linux, opensuse · leap 2020-04-09 medium4.8 CVE-2019-18905 A Insufficient Verification of Data Authenticity vulnerability in autoyast2 of SUSE Linux Enterprise Server 12, SUSE Linux Enterprise Server 15 allows remote a… opensuse · autoyast2 2020-04-03 medium6.5 CVE-2019-18904 A Uncontrolled Resource Consumption vulnerability in rmt of SUSE Linux Enterprise High Performance Computing 15-ESPOS, SUSE Linux Enterprise High Performance C… opensuse · rmt-server 2020-04-03 medium4.4 CVE-2020-11494 An issue was discovered in slc_bump in drivers/net/can/slcan.c in the Linux kernel 3.16 through 5.6.2. linux · linux_kernel, opensuse · leap, debian · debian_linux +1 2020-04-02 medium6.2 CVE-2020-8017 A Race Condition Enabling Link Following vulnerability in the cron job shipped with texlive-filesystem of SUSE Linux Enterprise Module for Desktop Applications… opensuse · texlive-filesystem, opensuse · leap 2020-04-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.