NetSight

Security Dashboard

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

Reset
1,364 matching advisories · page 3 of 46Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 medium6.5 CVE-2020-6565 Inappropriate implementation in Omnibox in Google Chrome on iOS prior to 85.0.4183.83 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) … google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 medium6.5 CVE-2020-6564 Inappropriate implementation in permissions in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to spoof the contents of a permission dialog via a… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 medium6.5 CVE-2020-6563 Insufficient policy enforcement in intent handling in Google Chrome on Android prior to 85.0.4183.83 allowed a remote attacker to obtain potentially sensitive … google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 medium6.5 CVE-2020-6562 Insufficient policy enforcement in Blink 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 medium6.5 CVE-2020-6561 Inappropriate implementation in Content Security Policy in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to leak cross-origin data via a crafte… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 medium6.5 CVE-2020-6560 Insufficient policy enforcement in autofill 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 medium6.5 CVE-2020-6558 Insufficient policy enforcement in iOSWeb in Google Chrome on iOS prior to 85.0.4183.83 allowed a remote attacker to bypass navigation restrictions via a craft… google · chrome, opensuse · backports_sle, opensuse · leap +1 2020-09-21 medium4.3 CVE-2020-15966 Insufficient policy enforcement in extensions in Google Chrome prior to 85.0.4183.121 allowed an attacker who convinced a user to install a malicious extension… google · chrome, debian · debian_linux, opensuse · backports_sle +2 2020-09-21 medium4.3 CVE-2020-15959 Insufficient policy enforcement in networking in Google Chrome prior to 85.0.4183.102 allowed an attacker who convinced the user to enable logging to obtain po… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-09-21 medium6.7 CVE-2020-0431 In kbd_keycode of keyboard.c, there is a possible out of bounds write due to a missing bounds check. google · android, opensuse · leap 2020-09-17 medium5.5 CVE-2020-0427 In create_pinctrl of core.c, there is a possible out of bounds read due to a use after free. google · android, debian · debian_linux, opensuse · leap +1 2020-09-17 medium4.7 CVE-2019-20919 An issue was discovered in the DBI module before 1.643 for Perl. perl · dbi, fedoraproject · fedora, canonical · ubuntu_linux +2 2020-09-17 medium5.5 CVE-2020-14392 An untrusted pointer dereference flaw was found in Perl-DBI < 1.643. perl · database_interface, canonical · ubuntu_linux, opensuse · leap +2 2020-09-16 medium6.7 CVE-2020-14386 A flaw was found in the Linux kernel before 5.9-rc4. linux · linux_kernel, debian · debian_linux, fedoraproject · fedora +1 2020-09-16 medium4.1 CVE-2020-25284 The rbd block device driver in drivers/block/rbd.c in the Linux kernel through 5.8.9 used incomplete permission checking for access to rbd devices, which could… linux · linux_kernel, debian · debian_linux, opensuse · leap 2020-09-13 medium4.4 CVE-2020-14342 It was found that cifs-utils' mount.cifs was invoking a shell when requesting the Samba password, which could be used to inject arbitrary commands. samba · cifs-utils, fedoraproject · fedora, opensuse · leap 2020-09-09 medium6.5 CVE-2020-24977 GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. xmlsoft · libxml2, debian · debian_linux, fedoraproject · fedora +9 2020-09-04 medium6.1 CVE-2020-24553 Go before 1.14.8 and 1.15.x before 1.15.1 allows XSS because text/html is the default for CGI/FCGI handlers that lack a Content-Type header. golang · go, fedoraproject · fedora, opensuse · leap +1 2020-09-02 medium6.5 CVE-2020-15811 An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. squid-cache · squid, canonical · ubuntu_linux, debian · debian_linux +2 2020-09-02 medium6.5 CVE-2020-15810 An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. squid-cache · squid, canonical · ubuntu_linux, debian · debian_linux +2 2020-09-02 medium6.5 CVE-2018-12475 A Externally Controlled Reference to a Resource in Another Sphere vulnerability in obs-service-download_files of openSUSE Open Build Service allows authenticat… opensuse · open_build_service 2020-09-01

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.