NetSight

Security Dashboard

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

Reset
1,646 matching advisories · page 42 of 55Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.7 CVE-2020-13314 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium4.3 CVE-2020-13313 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.5 CVE-2020-13312 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium4.3 CVE-2020-13311 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.4 CVE-2020-13318 A vulnerability was discovered in GitLab versions before 13.0.12, 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium5.4 CVE-2020-13316 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 high8.0 CVE-2020-13300 GitLab CE/EE version 13.3 prior to 13.3.4 was vulnerable to an OAuth authorization scope change without user consent in the middle of the authorization flow. gitlab · gitlab 2020-09-14 high8.1 CVE-2020-13299 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium5.4 CVE-2020-13289 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium4.3 CVE-2020-13287 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.5 CVE-2020-13284 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.4 CVE-2020-13286 For GitLab before 13.0.12, 13.1.6, 13.2.3 user controlled git configuration settings can be modified to result in Server Side Request Forgery. gitlab · gitlab 2020-08-13 medium6.5 CVE-2020-13281 For GitLab before 13.0.12, 13.1.6, 13.2.3 a denial of service exists in the project import feature gitlab · gitlab 2020-08-13 high7.3 CVE-2020-13285 For GitLab before 13.0.12, 13.1.6, 13.2.3 a cross-site scripting (XSS) vulnerability exists in the issue reference number tooltip. gitlab · gitlab 2020-08-13 high7.3 CVE-2020-13283 For GitLab before 13.0.12, 13.1.6, 13.2.3 a cross-site scripting vulnerability exists in the issues list via milestone title. gitlab · gitlab 2020-08-13 low3.1 CVE-2020-13282 For GitLab before 13.0.12, 13.1.6, 13.2.3 after a group transfer occurs, members from a parent group keep their access level on the subgroup leading to imprope… gitlab · gitlab 2020-08-13 medium6.5 CVE-2020-13280 For GitLab before 13.0.12, 13.1.6, 13.2.3 a memory exhaustion flaw exists due to excessive logging of an invite email error message. gitlab · gitlab 2020-08-13 critical10.0 CVE-2020-5415 Concourse, versions prior to 6.3.1 and 6.4.1, in installations which use the GitLab auth connector, is vulnerable to identity spoofing by way of configuring a … go · github.com/concourse/concourse, go · github.com/concourse/dex 2020-08-12 high8.1 CVE-2020-13291 In GitLab before 13.2.3, project sharing could temporarily allow too permissive access. gitlab · gitlab 2020-08-12 high7.5 CVE-2020-13290 In GitLab before 13.0.12, 13.1.6, and 13.2.3, improper access control was used on the Applications page gitlab · gitlab 2020-08-12 medium5.5 CVE-2020-13288 In GitLab before 13.0.12, 13.1.6, and 13.2.3, a stored XSS vulnerability exists in the CI/CD Jobs page gitlab · gitlab 2020-08-12 medium5.4 CVE-2020-13295 For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is susceptible to SSRF. gitlab · runner 2020-08-10 medium4.2 CVE-2020-13294 In GitLab before 13.0.12, 13.1.6 and 13.2.3, access grants were not revoked when a user revoked access to an application. gitlab · gitlab 2020-08-10 medium6.3 CVE-2020-13293 In GitLab before 13.0.12, 13.1.6 and 13.2.3 using a branch with a hexadecimal name could override an existing hash. gitlab · gitlab 2020-08-10 critical9.6 CVE-2020-13292 In GitLab before 13.0.12, 13.1.6 and 13.2.3, it is possible to bypass E-mail verification which is required for OAuth Flow. gitlab · gitlab 2020-08-10 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 medium5.3 CVE-2020-15525 GitLab EE 11.3 through 13.1.2 has Incorrect Access Control because of the Maven package upload endpoint. gitlab · gitlab 2020-07-07 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 medium5.3 CVE-2020-13264 Kubernetes cluster token disclosure in GitLab CE/EE 10.3 and later through 13.0.1 allows other group maintainers to view Kubernetes cluster token gitlab · gitlab 2020-06-19 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

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.