NetSight

Security Dashboard

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

Reset
4,088 matching advisories · page 24 of 137Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.0 CVE-2020-11039 In FreeRDP less than or equal to 2.0.0, when using a manipulated server with USB redirection enabled (nearly) arbitrary memory can be read and written due to i… freerdp · freerdp, opensuse · leap, debian · debian_linux 2020-05-29 medium6.9 CVE-2020-11038 In FreeRDP less than or equal to 2.0.0, an Integer Overflow to Buffer Overflow exists. freerdp · freerdp, opensuse · leap, debian · debian_linux 2020-05-29 medium4.3 CVE-2020-11019 In FreeRDP less than or equal to 2.0.0, when running with logger set to "WLOG_TRACE", a possible crash of application could occur due to a read of an invalid a… freerdp · freerdp, opensuse · leap, debian · debian_linux 2020-05-29 medium6.5 CVE-2020-11018 In FreeRDP less than or equal to 2.0.0, a possible resource exhaustion vulnerability can be performed. freerdp · freerdp, opensuse · leap, debian · debian_linux 2020-05-29 medium6.5 CVE-2020-11017 In FreeRDP less than or equal to 2.0.0, by providing manipulated input a malicious client can create a double free condition and crash the server. freerdp · freerdp, opensuse · leap, debian · debian_linux 2020-05-29 low3.2 CVE-2020-13362 In QEMU 5.0.0 and earlier, megasas_lookup_frame in hw/scsi/megasas.c has an out-of-bounds read via a crafted reply_queue_head field from a guest OS user. qemu · qemu, debian · debian_linux, opensuse · leap +1 2020-05-28 low3.9 CVE-2020-13361 In QEMU 5.0.0 and earlier, es1370_transfer_audio in hw/audio/es1370.c does not properly validate the frame count, which allows guest OS users to trigger an out… qemu · qemu, debian · debian_linux, opensuse · leap +1 2020-05-28 medium5.3 CVE-2019-20807 In Vim before 8.1.0881, users can circumvent the rvim restricted mode and execute arbitrary OS commands via scripting interfaces (e.g., Python, Ruby, or Lua). vim · vim, debian · debian_linux, opensuse · leap +4 2020-05-28 medium5.9 CVE-2020-13614 An issue was discovered in ssl.c in Axel before 2.17.8. axel_project · axel, fedoraproject · fedora, opensuse · backports_sle +1 2020-05-26 critical9.8 CVE-2020-6831 A buffer overflow could occur when parsing and validating SCTP chunks in WebRTC. mozilla · firefox, mozilla · firefox_esr, mozilla · thunderbird +3 2020-05-26 high7.5 CVE-2020-8164 Possible Strong Parameters Bypass in ActionPack rubygems · actionpack 2020-05-26 critical9.8 CVE-2020-8165 ActiveSupport potentially unintended unmarshalling of user-provided objects in MemCacheStore and RedisCacheStore rubygems · activesupport 2020-05-26 high8.3 CVE-2020-13398 An issue was discovered in FreeRDP before 2.1.1. freerdp · freerdp, canonical · ubuntu_linux, debian · debian_linux +1 2020-05-22 medium5.5 CVE-2020-13397 An issue was discovered in FreeRDP before 2.1.1. freerdp · freerdp, canonical · ubuntu_linux, debian · debian_linux +1 2020-05-22 high7.1 CVE-2020-13396 An issue was discovered in FreeRDP before 2.1.1. freerdp · freerdp, canonical · ubuntu_linux, debian · debian_linux +1 2020-05-22 medium5.9 CVE-2020-10711 A NULL pointer dereference flaw was found in the Linux kernel's SELinux subsystem in versions before 5.7. linux · linux_kernel, redhat · 3scale, redhat · openstack +8 2020-05-22 medium6.8 CVE-2020-11077 HTTP Smuggling via Transfer-Encoding Header in Puma rubygems · puma 2020-05-22 high8.1 CVE-2020-12693 Slurm 19.05.x before 19.05.7 and 20.02.x before 20.02.3, in the rare case where Message Aggregation is enabled, allows Authentication Bypass via an Alternate P… schedmd · slurm, fedoraproject · fedora, opensuse · leap +1 2020-05-21 high8.2 CVE-2020-13113 An issue was discovered in libexif before 0.6.22. libexif_project · libexif, debian · debian_linux, canonical · ubuntu_linux +1 2020-05-21 high7.5 CVE-2020-13114 An issue was discovered in libexif before 0.6.22. libexif_project · libexif, canonical · ubuntu_linux, opensuse · leap 2020-05-21 critical9.1 CVE-2020-13112 An issue was discovered in libexif before 0.6.22. libexif_project · libexif, debian · debian_linux, canonical · ubuntu_linux +1 2020-05-21 medium6.5 CVE-2020-6491 Insufficient data validation in site information in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof security UI via a crafted domain nam… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium4.3 CVE-2020-6490 Insufficient data validation in loader in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had been able to write to disk to leak cross-origin… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium4.3 CVE-2020-6489 Inappropriate implementation in developer tools in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had convinced the user to take certain act… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium4.3 CVE-2020-6488 Insufficient policy enforcement in downloads in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted H… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium6.5 CVE-2020-6487 Insufficient policy enforcement in downloads in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted H… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium6.5 CVE-2020-6486 Insufficient policy enforcement in navigations in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium6.5 CVE-2020-6485 Insufficient data validation in media router in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had compromised the renderer process to bypas… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium6.5 CVE-2020-6484 Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted r… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-21 medium6.5 CVE-2020-6483 Insufficient policy enforcement in payments in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a crafted HT… google · chrome, opensuse · backports_sle, debian · debian_linux +2 2020-05-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.