NetSight

Security Dashboard

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

Reset
1,002 matching advisories · page 24 of 34Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.0 CVE-2021-22178 An issue has been discovered in GitLab affecting all versions starting from 13.2. gitlab · gitlab 2021-03-24 medium4.3 CVE-2021-22176 An issue has been discovered in GitLab affecting all versions starting with 3.0.1. gitlab · gitlab 2021-03-24 medium5.9 CVE-2021-22189 Starting with version 13.7 the Gitlab CE/EE editions were affected by a security issue related to the validation of the certificates for the Fortinet OTP that … gitlab · gitlab 2021-03-04 medium4.1 CVE-2021-22183 An issue has been discovered in GitLab affecting all versions starting with 11.8. gitlab · gitlab 2021-03-04 medium5.3 CVE-2021-22188 An issue has been discovered in GitLab affecting all versions starting with 13.0. gitlab · gitlab 2021-03-03 medium4.3 CVE-2021-22187 An issue has been discovered in GitLab affecting all versions of Gitlab EE/CE before 13.6.7. gitlab · gitlab 2021-03-02 medium4.3 CVE-2021-22168 A regular expression denial of service issue has been discovered in NuGet API affecting all versions of GitLab starting from version 12.8. gitlab · gitlab 2021-01-15 medium5.3 CVE-2021-22167 An issue has been discovered in GitLab affecting all versions starting from 12.1. gitlab · gitlab 2021-01-15 medium5.3 CVE-2021-22166 An attacker could cause a Prometheus denial of service in GitLab 13.7+ by sending an HTTP request with a malformed method gitlab · gitlab 2021-01-15 medium4.3 CVE-2020-26414 An issue has been discovered in GitLab affecting all versions starting from 12.4. gitlab · gitlab 2021-01-15 medium5.3 CVE-2020-35236 The GitLab Webhook Handler in amazee.io Lagoon before 1.12.3 has incorrect access control associated with project deletion. amazee · lagoon 2020-12-14 medium4.3 CVE-2020-26411 A potential DOS vulnerability was discovered in all versions of Gitlab starting from 13.4.x (>=13.4 to <13.4.7, >=13.5 to <13.5.5, and >=13.6 to <13.6.2). gitlab · gitlab 2020-12-11 medium5.3 CVE-2020-26417 Information disclosure via GraphQL in GitLab CE/EE 13.1 and later exposes private group and project membership. gitlab · gitlab 2020-12-11 medium4.0 CVE-2020-26416 Information disclosure in Advanced Search component of GitLab EE starting from 8.4 results in exposure of search terms via Rails logs. gitlab · gitlab 2020-12-11 medium4.3 CVE-2020-26415 Information about the starred projects for private user profiles was exposed via the GraphQL API starting from 12.2 via the REST API. gitlab · gitlab 2020-12-11 medium5.3 CVE-2020-26413 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4 before 13.6.2. gitlab · gitlab 2020-12-11 medium5.3 CVE-2020-26408 A limited information disclosure vulnerability exists in Gitlab CE/EE from >= 12.2 to <13.4.7, >=13.5 to <13.5.5, and >=13.6 to <13.6.2 that allows an attacker… gitlab · gitlab 2020-12-11 medium4.3 CVE-2020-13357 An issue was discovered in Gitlab CE/EE versions >= 13.1 to <13.4.7, >= 13.5 to <13.5.5, and >= 13.6 to <13.6.2 allowed an unauthorized user to access the user… gitlab · gitlab 2020-12-11 medium4.3 CVE-2020-26409 A DOS vulnerability exists in Gitlab CE/EE >=10.3, <13.4.7,>=13.5, <13.5.5,>=13.6, <13.6.2 that allows an attacker to trigger uncontrolled resource by bypassin… gitlab · gitlab 2020-12-11 medium5.5 CVE-2020-26407 A XSS vulnerability exists in Gitlab CE/EE from 12.4 before 13.4.7, 13.5 before 13.5.5, and 13.6 before 13.6.2 that allows an attacker to perform cross-site sc… gitlab · gitlab 2020-12-10 medium4.3 CVE-2020-13349 An issue has been discovered in GitLab EE affecting all versions starting from 8.12. gitlab · gitlab 2020-11-17 medium5.7 CVE-2020-13348 An issue has been discovered in GitLab EE affecting all versions starting from 10.2. gitlab · gitlab 2020-11-17 medium6.5 CVE-2020-13351 Insufficient permission checks in scheduled pipeline API in GitLab CE/EE 13.0+ allows an attacker to read variable names and values for scheduled pipelines on … gitlab · gitlab 2020-11-17 medium5.3 CVE-2020-26406 Certain SAST CiConfiguration information could be viewed by unauthorized users in GitLab EE starting with 13.3. gitlab · gitlab 2020-11-17 medium4.7 CVE-2020-13358 A vulnerability in the internal Kubernetes agent api in GitLab CE/EE version 13.3 and above allows unauthorized access to private projects. gitlab · gitlab 2020-11-17 medium4.3 CVE-2020-13354 A potential DOS vulnerability was discovered in GitLab CE/EE starting with version 12.6. gitlab · gitlab 2020-11-17 medium6.0 CVE-2020-13327 An issue has been discovered in GitLab Runner affecting all versions starting from 13.4.0 before 13.4.2, all versions starting from 13.3.0 before 13.3.7, all v… gitlab · runner 2020-10-22 medium4.9 CVE-2020-13341 An issue has been discovered in GitLab affecting all versions prior to 13.2.10, 13.3.7 and 13.4.2. gitlab · gitlab 2020-10-12 medium5.7 CVE-2020-13344 An issue has been discovered in GitLab affecting all versions prior to 13.2.10, 13.3.7 and 13.4.2. gitlab · gitlab 2020-10-08 medium5.5 CVE-2020-13339 An issue has been discovered in GitLab affecting all versions before 13.2.10, 13.3.7 and 13.4.2: XSS in SVG File Preview. gitlab · gitlab 2020-10-08

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.