NetSight

Security Dashboard

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

Reset
344 matching advisories · page 9 of 12Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2020-2228 Jenkins Gitlab Authentication Plugin 1.5 and earlier does not perform group authorization checks properly, resulting in a privilege escalation vulnerability. maven · org.jenkins-ci.plugins:gitlab-oauth 2020-07-15 high8.6 CVE-2020-13279 Client side code execution in gitlab-vscode-extension v2.2.0 allows attacker to execute code on user system gitlab · gitlab-vscode-extension 2020-06-22 high7.5 CVE-2020-13263 An authorization issue relating to project maintainer impersonation was identified in GitLab EE 9.5 and later through 13.0.1 that could allow unauthorized user… gitlab · gitlab 2020-06-19 high7.4 CVE-2020-13276 User is allowed to set an email as a notification email even without verifying the new email in all previous GitLab CE/EE versions through 13.0.1 gitlab · gitlab 2020-06-19 high8.0 CVE-2020-13275 A user with an unverified email address could request an access to domain restricted groups in GitLab EE 12.2 and later through 13.0.1 gitlab · gitlab 2020-06-19 high7.5 CVE-2020-13274 A security issue allowed achieving Denial of Service attacks through memory exhaustion by uploading malicious artifacts in all previous GitLab versions through… gitlab · gitlab 2020-06-19 high7.5 CVE-2020-13273 A Denial of Service vulnerability allowed exhausting the system resources in GitLab CE/EE 12.0 and later through 13.0.1 gitlab · gitlab 2020-06-19 high7.5 CVE-2020-13272 OAuth flow missing verification checks CE/EE 12.3 and later through 13.0.1 allows unverified user to use OAuth authorization code flow gitlab · gitlab 2020-06-19 high7.5 CVE-2020-13270 Missing permission check on fork relation creation in GitLab CE/EE 11.3 and later through 13.0.1 allows guest users to create a fork relation on restricted pub… gitlab · gitlab 2020-06-10 high7.5 CVE-2020-11506 An issue was discovered in GitLab 10.7.0 and later through 12.9.2. gitlab · gitlab 2020-04-22 high7.5 CVE-2020-11505 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) before 12.7.9, 12.8.x before 12.8.9, and 12.9.x before 12.9.3. gitlab · gitlab 2020-04-22 high7.5 CVE-2020-10976 GitLab EE/CE 8.17 to 12.9 is vulnerable to information leakage when querying a merge request widget. gitlab · gitlab 2020-04-08 high7.5 CVE-2020-10954 GitLab through 12.9 is affected by a potential DoS in repository archive download. gitlab · gitlab 2020-03-27 high7.5 CVE-2020-10953 In GitLab EE 11.7 through 12.9, the NPM feature is vulnerable to a path traversal issue. gitlab · gitlab 2020-03-27 high7.5 CVE-2020-10073 GitLab EE 12.4.2 through 12.8.1 allows Denial of Service. gitlab · gitlab 2020-03-13 high7.5 CVE-2020-10089 GitLab 8.11 through 12.8.1 allows a Denial of Service when using several features to recursively request eachother, gitlab · gitlab 2020-03-13 high8.1 CVE-2020-10088 GitLab 12.5 through 12.8.1 has Insecure Permissions. gitlab · gitlab 2020-03-13 high7.5 CVE-2020-10087 GitLab before 12.8.2 allows Information Disclosure. gitlab · gitlab 2020-03-13 high7.5 CVE-2019-13121 An issue was discovered in GitLab Enterprise Edition 10.6 through 12.0.2. gitlab · gitlab 2020-03-10 high7.5 CVE-2019-13003 An issue was discovered in GitLab Community and Enterprise Edition before 12.0.3. gitlab · gitlab 2020-03-10 high7.5 CVE-2019-12446 An issue was discovered in GitLab Community and Enterprise Edition 8.3 through 11.11. gitlab · gitlab 2020-03-10 high7.5 CVE-2019-12441 An issue was discovered in GitLab Community and Enterprise Edition 8.4 through 11.11. gitlab · gitlab 2020-03-10 high8.8 CVE-2019-12430 An issue was discovered in GitLab Community and Enterprise Edition 11.11. gitlab · gitlab 2020-03-10 high7.5 CVE-2020-8795 In GitLab Enterprise Edition (EE) 12.5.0 through 12.7.5, sharing a group with a group could grant project access to unauthorized users. gitlab · gitlab 2020-02-17 high7.5 CVE-2020-6833 An issue was discovered in GitLab EE 11.3 and later. gitlab · gitlab 2020-02-05 high7.5 CVE-2020-7978 GitLab EE 12.6 and later through 12.7.2 allows Denial of Service. gitlab · gitlab 2020-02-05 high7.5 CVE-2020-7972 GitLab EE 12.2 has Insecure Permissions (issue 2 of 2). gitlab · gitlab 2020-02-05 high7.5 CVE-2020-7969 GitLab EE 8.0 and later through 12.7.2 allows Information Disclosure. gitlab · gitlab 2020-02-05 high7.5 CVE-2020-7968 GitLab EE 8.0 through 12.7.2 has Incorrect Access Control. gitlab · gitlab 2020-02-05 high7.5 CVE-2020-7966 GitLab EE 11.11 and later through 12.7.2 allows Directory Traversal. gitlab · gitlab 2020-02-05

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.