NetSight

Security Dashboard

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

Reset
4,088 matching advisories · page 25 of 137Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2020-6482 Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malicious exten… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-05-21 medium6.5 CVE-2020-6481 Insufficient policy enforcement in URL formatting in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to perform domain spoofing via a crafted dom… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-05-21 medium6.5 CVE-2020-6480 Insufficient policy enforcement in enterprise in Google Chrome prior to 83.0.4103.61 allowed a local attacker to bypass navigation restrictions via UI actions. google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-05-21 medium6.5 CVE-2020-6479 Inappropriate implementation in sharing in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof security UI via a crafted HTML page. google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium6.5 CVE-2020-6478 Inappropriate implementation in full screen in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof security UI via a crafted HTML page. google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 high7.8 CVE-2020-6477 Inappropriate implementation in installer in Google Chrome on OS X prior to 83.0.4103.61 allowed a local attacker to perform privilege escalation via a crafted… google · chrome, fedoraproject · fedora, opensuse · backports_sle +1 2020-05-21 medium6.5 CVE-2020-6476 Insufficient policy enforcement in tab strip in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malicious extension t… google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-05-21 medium6.5 CVE-2020-6475 Incorrect implementation in full screen in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof security UI via a crafted HTML page. google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-05-21 high8.8 CVE-2020-6474 Use after free in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. google · chrome, opensuse · backports_sle, opensuse · leap +2 2020-05-21 medium6.5 CVE-2020-6473 Insufficient policy enforcement in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to obtain potentially sensitive information from proc… google · chrome, fedoraproject · fedora, opensuse · backports_sle +2 2020-05-21 medium6.5 CVE-2020-6472 Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malicious exten… google · chrome, fedoraproject · fedora, opensuse · backports_sle +2 2020-05-21 critical9.6 CVE-2020-6471 Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malicious exten… google · chrome, fedoraproject · fedora, opensuse · backports_sle +2 2020-05-21 medium6.1 CVE-2020-6470 Insufficient validation of untrusted input in clipboard in Google Chrome prior to 83.0.4103.61 allowed a local attacker to inject arbitrary scripts or HTML (UX… google · chrome, fedoraproject · fedora, opensuse · backports_sle +2 2020-05-21 critical9.6 CVE-2020-6469 Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malicious exten… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 high8.8 CVE-2020-6468 Type confusion in V8 in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. google · chrome, fedoraproject · fedora, debian · debian_linux +2 2020-05-21 high8.8 CVE-2020-6467 Use after free in WebRTC in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 critical9.6 CVE-2020-6466 Use after free in media in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had compromised the renderer process to potentially perform a sand… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 critical9.6 CVE-2020-6465 Use after free in reader mode in Google Chrome on Android prior to 83.0.4103.61 allowed a remote attacker who had compromised the renderer process to potential… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 high8.8 CVE-2020-6464 Type confusion in Blink in Google Chrome prior to 81.0.4044.138 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. google · chrome, debian · debian_linux, opensuse · leap 2020-05-21 high8.8 CVE-2020-6463 Use after free in ANGLE in Google Chrome prior to 81.0.4044.122 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. google · chrome, fedoraproject · fedora, canonical · ubuntu_linux +3 2020-05-21 high7.0 CVE-2020-9484 When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the con… maven · org.apache.tomcat:tomcat-catalina, maven · org.apache.tomcat.embed:tomcat-embed-core 2020-05-20 high8.8 CVE-2020-13249 libmariadb/mariadb_lib.c in MariaDB Connector/C before 3.1.8 does not properly validate the content of an OK packet received from a server. mariadb · connector\/c, opensuse · leap, fedoraproject · fedora 2020-05-20 medium6.0 CVE-2020-10726 A vulnerability was found in DPDK versions 19.11 and above. dpdk · data_plane_development_kit, fedoraproject · fedora, opensuse · leap +1 2020-05-20 high7.7 CVE-2020-10725 A flaw was found in DPDK version 19.11 and above that allows a malicious guest to cause a segmentation fault of the vhost-user backend application running on t… dpdk · data_plane_development_kit, fedoraproject · fedora, opensuse · leap +1 2020-05-20 high7.5 CVE-2020-13164 In Wireshark 3.2.0 to 3.2.3, 3.0.0 to 3.0.10, and 2.6.0 to 2.6.16, the NFS dissector could crash. wireshark · wireshark, debian · debian_linux, opensuse · leap +1 2020-05-19 medium5.1 CVE-2020-10723 A memory corruption issue was found in DPDK versions 17.05 and above. dpdk · data_plane_development_kit, canonical · ubuntu_linux, fedoraproject · fedora +3 2020-05-19 medium5.1 CVE-2020-10722 A vulnerability was found in DPDK versions 18.05 and above. dpdk · data_plane_development_kit, canonical · ubuntu_linux, fedoraproject · fedora +3 2020-05-19 high7.5 CVE-2020-10995 PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. powerdns · recursor, fedoraproject · fedora, debian · debian_linux +2 2020-05-19 medium5.4 CVE-2020-10135 Legacy pairing and secure-connections pairing authentication in Bluetooth BR/EDR Core Specification v5.2 and earlier may allow an unauthenticated user to compl… bluetooth · bluetooth_core, opensuse · leap 2020-05-19 medium5.3 CVE-2020-8021 a Improper Access Control vulnerability in of Open Build Service allows remote attackers to read files of an OBS package where the sourceaccess/access is disab… opensuse · open_build_service, debian · debian_linux 2020-05-19

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.