NetSight

Security Dashboard

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

Reset
4,088 matching advisories · page 14 of 137Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2020-15203 Denial of Service in Tensorflow pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2020-09-25 critical9.0 CVE-2020-15202 Integer truncation in Shard API usage pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2020-09-25 high8.5 CVE-2020-15195 Heap buffer overflow in Tensorflow pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2020-09-25 high7.1 CVE-2020-15193 Memory corruption in Tensorflow pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2020-09-25 medium5.3 CVE-2020-15191 Undefined behavior in Tensorflow pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2020-09-25 medium5.3 CVE-2020-15194 Denial of Service in Tensorflow pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2020-09-25 medium4.3 CVE-2020-15192 Memory leak in Tensorflow pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2020-09-25 medium5.3 CVE-2020-15190 Segfault in Tensorflow pip · tensorflow, pip · tensorflow-cpu, pip · tensorflow-gpu 2020-09-25 medium6.1 CVE-2019-11556 Pagure before 5.6 allows XSS via the templates/blame.html blame view. redhat · pagure, opensuse · backports_sle, opensuse · leap 2020-09-25 medium5.5 CVE-2020-26088 A missing CAP_NET_RAW check in NFC socket creation in net/nfc/rawsock.c in the Linux kernel before 5.8.2 could be used by local attackers to create raw sockets… linux · linux_kernel, debian · debian_linux, opensuse · leap +1 2020-09-24 medium4.7 CVE-2020-25604 An issue was discovered in Xen through 4.14.x. xen · xen, fedoraproject · fedora, debian · debian_linux +1 2020-09-23 high7.8 CVE-2020-25603 An issue was discovered in Xen through 4.14.x. xen · xen, fedoraproject · fedora, opensuse · leap +1 2020-09-23 medium6.0 CVE-2020-25602 An issue was discovered in Xen through 4.14.x. xen · xen, fedoraproject · fedora, debian · debian_linux +1 2020-09-23 medium5.5 CVE-2020-25601 An issue was discovered in Xen through 4.14.x. xen · xen, debian · debian_linux, fedoraproject · fedora +1 2020-09-23 medium5.5 CVE-2020-25600 An issue was discovered in Xen through 4.14.x. xen · xen, fedoraproject · fedora, opensuse · leap +1 2020-09-23 high7.0 CVE-2020-25599 An issue was discovered in Xen through 4.14.x. xen · xen, fedoraproject · fedora, opensuse · leap +1 2020-09-23 medium5.5 CVE-2020-25598 An issue was discovered in Xen 4.14.x. xen · xen, fedoraproject · fedora, opensuse · leap 2020-09-23 medium5.5 CVE-2020-25596 An issue was discovered in Xen through 4.14.x. xen · xen, fedoraproject · fedora, debian · debian_linux +1 2020-09-23 high7.8 CVE-2020-25595 An issue was discovered in Xen through 4.14.x. xen · xen, fedoraproject · fedora, debian · debian_linux +1 2020-09-23 medium5.9 CVE-2020-24619 In mainwindow.cpp in Shotcut before 20.09.13, the upgrade check misuses TLS because of setPeerVerifyMode(QSslSocket::VerifyNone). meltytech · shotcut 2020-09-22 high8.8 CVE-2020-6576 Use after free in offscreen canvas in Google Chrome prior to 85.0.4183.102 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML … google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 high8.3 CVE-2020-6575 Race in Mojo in Google Chrome prior to 85.0.4183.102 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 high7.8 CVE-2020-6574 Insufficient policy enforcement in installer in Google Chrome on OS X prior to 85.0.4183.102 allowed a local attacker to potentially achieve privilege escalati… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-09-21 critical9.6 CVE-2020-6573 Use after free in video in Google Chrome on Android prior to 85.0.4183.102 allowed a remote attacker who had compromised the renderer process to potentially pe… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 medium4.3 CVE-2020-6571 Insufficient data validation in Omnibox in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to perform domain spoofing via IDN homographs via a cr… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-09-21 medium4.3 CVE-2020-6570 Information leakage in WebRTC in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to obtain potentially sensitive information via a crafted WebRTC… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-09-21 medium6.3 CVE-2020-6569 Integer overflow in WebUSB in Google Chrome prior to 85.0.4183.83 allowed a remote attacker who had compromised the renderer process to potentially exploit hea… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 medium6.5 CVE-2020-6568 Insufficient policy enforcement in intent handling in Google Chrome on Android prior to 85.0.4183.83 allowed a remote attacker to bypass navigation restriction… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 medium6.5 CVE-2020-6567 Insufficient validation of untrusted input in command line handling in Google Chrome on Windows prior to 85.0.4183.83 allowed a remote attacker to bypass navig… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 medium6.5 CVE-2020-6566 Insufficient policy enforcement in media in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to leak cross-origin data via a crafted HTML page. google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21

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.