NetSight

Security Dashboard

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

Reset
1,002 matching advisories · page 28 of 34Index updated 9 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2019-12825 Unauthorized Access to the Container Registry of other groups was discovered in GitLab Enterprise 12.0.0-pre. gitlab · gitlab 2020-02-17 medium4.3 CVE-2019-15594 GitLab 11.8 and later contains a security vulnerability that allows a user to obtain details of restricted pipelines via the merge request endpoint. gitlab · gitlab 2020-02-14 medium4.3 CVE-2019-15592 GitLab 12.2.2 and below contains a security vulnerability that allows a guest user in a private project to see the merge request ID associated to an issue via … gitlab · gitlab 2020-02-14 medium5.3 CVE-2020-7977 GitLab EE 8.8 and later through 12.7.2 has Insecure Permissions. gitlab · gitlab 2020-02-05 medium5.3 CVE-2020-7976 GitLab EE 12.4 and later through 12.7.2 has Incorrect Access Control. gitlab · gitlab 2020-02-05 medium5.3 CVE-2020-7974 GitLab EE 10.1 through 12.7.2 allows Information Disclosure. gitlab · gitlab 2020-02-05 medium6.1 CVE-2020-7973 GitLab through 12.7.2 allows XSS. gitlab · gitlab 2020-02-05 medium6.1 CVE-2020-7971 GitLab EE 11.0 and later through 12.7.2 allows XSS. gitlab · gitlab 2020-02-05 medium4.3 CVE-2020-7967 GitLab EE 8.0 through 12.7.2 has Insecure Permissions (issue 1 of 2). gitlab · gitlab 2020-02-05 medium5.3 CVE-2020-7979 GitLab EE 8.9 and later through 12.7.2 has Insecure Permission gitlab · gitlab 2020-02-05 medium6.5 CVE-2013-4582 The (1) create_branch, (2) create_tag, (3) import_project, and (4) fork_project functions in lib/gitlab_projects.rb in GitLab 5.0 before 5.4.2, Community Editi… gitlab · gitlab, gitlab · gitlab-shell 2020-01-28 medium6.5 CVE-2019-5474 An authorization issue was discovered in GitLab EE < 12.1.2, < 12.0.4, and < 11.11.6 allowing the merge request approval rules to be overridden without appropr… gitlab · gitlab 2020-01-28 medium4.3 CVE-2019-5466 An IDOR was discovered in GitLab CE/EE 11.5 and later that allowed new merge requests endpoint to disclose label names. gitlab · gitlab 2020-01-28 medium4.3 CVE-2019-5465 An information disclosure issue was discovered in GitLab CE/EE 8.14 and later, by using the move issue feature which could result in disclosure of the newly cr… gitlab · gitlab 2020-01-28 medium6.1 CVE-2019-15586 A XSS exists in Gitlab CE/EE < 12.1.10 in the Mermaid plugin. gitlab · gitlab 2020-01-28 medium5.3 CVE-2019-15582 An IDOR was discovered in < 12.3.2, < 12.2.6, and < 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE) that allowed a maintainer to add any … gitlab · gitlab 2020-01-28 medium5.3 CVE-2019-15581 An IDOR exists in < 12.3.2, < 12.2.6, and < 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE) that allowed a project owner or maintainer to… gitlab · gitlab 2020-01-28 medium5.3 CVE-2019-15579 An information disclosure exists in < 12.3.2, < 12.2.6, and < 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE) where the assignee(s) of a … gitlab · gitlab 2020-01-28 medium5.3 CVE-2019-15578 An information disclosure exists in < 12.3.2, < 12.2.6, and < 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE). gitlab · gitlab 2020-01-28 medium6.1 CVE-2020-2096 Jenkins Gitlab Hook Plugin 1.4.2 and earlier does not escape project names in the build_now endpoint, resulting in a reflected XSS vulnerability. maven · org.jenkins-ci.ruby-plugins:gitlab-hook 2020-01-15 medium4.3 CVE-2019-20144 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 10.8 through 12.6.1. gitlab · gitlab 2020-01-13 medium5.3 CVE-2019-20143 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 12.6. gitlab · gitlab 2020-01-13 medium4.3 CVE-2019-20142 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 12.3 through 12.6.1. gitlab · gitlab 2020-01-13 medium5.3 CVE-2020-6832 An issue was discovered in GitLab Enterprise Edition (EE) 8.9.0 through 12.6.1. gitlab · gitlab 2020-01-13 medium4.3 CVE-2020-5197 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 5.1 through 12.6.1. gitlab · gitlab 2020-01-13 medium5.3 CVE-2019-20148 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 8.13 through 12.6.1. gitlab · gitlab 2020-01-13 medium5.3 CVE-2019-20147 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 9.1 through 12.6.1. gitlab · gitlab 2020-01-13 medium5.3 CVE-2019-20146 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 11.0 through 12.6. gitlab · gitlab 2020-01-13 medium4.3 CVE-2019-20145 An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 11.4 through 12.6.1. gitlab · gitlab 2020-01-13 medium5.8 CVE-2019-19312 GitLab EE 8.14 through 12.5, 12.4.3, and 12.3.6 has Incorrect Access Control. gitlab · gitlab 2020-01-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.