NetSight

Security Dashboard

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

Reset
344 matching advisories · page 8 of 12Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2021-22241 An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.0. gitlab · gitlab 2021-08-05 high7.1 CVE-2021-22224 A cross-site request forgery vulnerability in the GraphQL API in GitLab since version 13.12 and before versions 13.12.6 and 14.0.2 allowed an attacker to call … gitlab · gitlab 2021-07-07 high7.7 CVE-2021-22181 A denial of service vulnerability in GitLab CE/EE affecting all versions since 11.8 allows an attacker to create a recursive pipeline relationship and exhaust … gitlab · gitlab 2021-06-11 high8.8 CVE-2021-22213 A cross-site leak vulnerability in the OAuth flow of all versions of GitLab CE/EE since 7.10 allowed an attacker to leak an OAuth access token by getting the v… gitlab · gitlab 2021-06-08 high7.5 CVE-2021-22215 An information disclosure vulnerability in GitLab EE versions 13.11 and later allowed a project owner to leak information about the members' on-call rotations … gitlab · gitlab 2021-06-08 high7.5 CVE-2021-22209 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.8. gitlab · gitlab 2021-05-06 high8.5 CVE-2021-22190 A path traversal vulnerability via the GitLab Workhorse in all versions of GitLab could result in the leakage of a JWT token gitlab · gitlab 2021-04-12 high7.5 CVE-2021-22203 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions starting from 13.9 before 13.9.5, and all … gitlab · gitlab 2021-04-02 high8.6 CVE-2021-22195 Client side code execution in gitlab-vscode-extension v3.15.0 and earlier allows attacker to execute code on user system gitlab · gitlab-vscode-extension 2021-04-01 high7.3 CVE-2021-22171 Insufficient validation of authentication parameters in GitLab Pages for GitLab 11.5+ allows an attacker to steal a victim's API token if they click on a malic… gitlab · gitlab 2021-01-15 high7.6 CVE-2020-13359 The Terraform API in GitLab CE/EE 12.10+ exposed the object storage signed URL on the delete operation allowing a malicious project maintainer to overwrite the… gitlab · gitlab 2020-11-19 high8.2 CVE-2020-13356 An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.8.9. gitlab · gitlab 2020-11-19 high7.5 CVE-2020-13355 An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.14. gitlab · gitlab 2020-11-19 high7.1 CVE-2020-26405 Path traversal vulnerability in package upload functionality in GitLab CE/EE starting from 12.8 allows an attacker to save packages in arbitrary locations. gitlab · gitlab 2020-11-17 high7.5 CVE-2020-27986 SonarQube 8.4.2.36762 allows remote attackers to discover cleartext SMTP, SVN, and GitLab credentials via the api/settings/values URI. sonarsource · sonarqube 2020-10-28 high8.7 CVE-2020-13340 An issue has been discovered in GitLab affecting all versions prior to 13.2.10, 13.3.7 and 13.4.2: Stored XSS in CI Job Log gitlab · gitlab 2020-10-08 high7.5 CVE-2020-13343 An issue has been discovered in GitLab affecting all versions starting from 11.2. gitlab · gitlab 2020-10-06 high7.2 CVE-2020-13337 An issue has been discovered in GitLab affecting versions from 12.10 to 12.10.12 that allowed for a stored XSS payload to be added as a group name. gitlab · gitlab 2020-10-02 high7.1 CVE-2020-13325 A vulnerability was discovered in GitLab versions prior 13.1. gitlab · gitlab 2020-09-30 high7.7 CVE-2020-13323 A vulnerability was discovered in GitLab versions prior 13.1. gitlab · gitlab 2020-09-30 high7.2 CVE-2020-13322 A vulnerability was discovered in GitLab versions after 12.9. gitlab · gitlab 2020-09-30 high8.3 CVE-2020-13321 A vulnerability was discovered in GitLab versions prior to 13.1. gitlab · gitlab 2020-09-30 high7.1 CVE-2020-13303 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-15 high7.2 CVE-2020-13298 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 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 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

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.