NetSight

Security Dashboard

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

Reset
4,088 matching advisories · page 15 of 137Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 high8.8 CVE-2020-6559 Use after free in presentation API in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML p… 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 high8.8 CVE-2020-6556 Heap buffer overflow in SwiftShader in Google Chrome prior to 84.0.4147.135 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML… google · chrome, debian · debian_linux, fedoraproject · fedora +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 high8.8 CVE-2020-15965 Type confusion in V8 in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML pa… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-09-21 high8.8 CVE-2020-15964 Insufficient data validation in media in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentially exploit heap corruption via a crafted HT… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-09-21 critical9.6 CVE-2020-15963 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, opensuse · backports_sle, opensuse · leap +2 2020-09-21 high8.8 CVE-2020-15962 Insufficient policy validation in serial in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentially perform out of bounds memory access v… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-09-21 critical9.6 CVE-2020-15961 Insufficient policy validation 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, opensuse · backports_sle, opensuse · leap +2 2020-09-21 high8.8 CVE-2020-15960 Heap buffer overflow in storage in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentially perform out of bounds memory access via a craf… google · chrome, opensuse · backports_sle, opensuse · leap +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 high7.8 CVE-2020-8252 The implementation of realpath in libuv < 10.22.1, < 12.18.4, and < 14.9.0 used within Node.js incorrectly determined the buffer size which can result in a buf… nodejs · node.js, opensuse · leap, fedoraproject · fedora 2020-09-18 high7.4 CVE-2020-8201 Node.js < 12.18.4 and < 14.11 can be exploited to perform HTTP desync attacks and deliver malicious payloads to unsuspecting users. nodejs · node.js, opensuse · leap, fedoraproject · fedora 2020-09-18 high7.8 CVE-2020-0432 In skb_to_mamac of networking.c, there is a possible out of bounds write due to an integer overflow. google · android, opensuse · leap 2020-09-17 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 critical9.3 CVE-2020-8028 A Improper Access Control vulnerability in the configuration of salt of SUSE Linux Enterprise Module for SUSE Manager Server 4.1, SUSE Manager Proxy 4.0, SUSE … suse · salt-netapi-client 2020-09-17 high8.8 CVE-2020-25040 Insecure permissions on build temporary rootfs in Singularity go · github.com/sylabs/singularity 2020-09-16 high8.1 CVE-2020-25039 Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity go · github.com/sylabs/singularity 2020-09-16 high7.1 CVE-2020-14393 A buffer overflow was found in perl-DBI < 1.643 in DBI.xs. perl · database_interface, opensuse · leap, debian · debian_linux +1 2020-09-16 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

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.