NetSight

Security Dashboard

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

Reset
1,646 matching advisories · page 22 of 55Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.7 CVE-2024-0199 An authorization bypass vulnerability was discovered in GitLab affecting versions 11.3 prior to 16.7.7, 16.7.6 prior to 16.8.4, and 16.8.3 prior to 16.9.2. gitlab · gitlab 2024-03-07 medium4.3 CVE-2023-4895 An issue has been discovered in GitLab EE affecting all versions starting from 12.0 to 16.7.6, all versions starting from 16.8 before 16.8.3, all versions star… gitlab · gitlab 2024-02-22 medium5.3 CVE-2024-1525 An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.1 before 16.7.6, all versions starting from 16.8 before 16.8.3, all versio… gitlab · gitlab 2024-02-22 high8.7 CVE-2024-1451 An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.9 before 16.9.1. gitlab · gitlab 2024-02-22 medium4.3 CVE-2024-0861 An issue has been discovered in GitLab EE affecting all versions starting from 16.4 before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions … gitlab · gitlab 2024-02-22 high7.7 CVE-2024-0410 An authorization bypass vulnerability was discovered in GitLab affecting versions 15.1 prior to 16.7.6, 16.8 prior to 16.8.3, and 16.9 prior to 16.9.1. gitlab · gitlab 2024-02-22 medium6.7 CVE-2023-6477 An issue has been discovered in GitLab EE affecting all versions starting from 16.5 before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions … gitlab · gitlab 2024-02-22 low3.7 CVE-2023-3509 An issue has been discovered in GitLab affecting all versions before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions starting from 16.9 bef… gitlab · gitlab 2024-02-21 medium6.5 CVE-2024-1250 An issue has been discovered in GitLab EE affecting all versions starting from 16.8 before 16.8.2. gitlab · gitlab 2024-02-12 medium6.5 CVE-2023-6564 An issue has been discovered in GitLab EE Premium and Ultimate affecting versions 16.4.3, 16.5.3, and 16.6.1. gitlab · gitlab 2024-02-08 medium6.5 CVE-2024-1066 An issue has been discovered in GitLab EE affecting all versions from 13.3.0 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2 which allows an at… gitlab · gitlab 2024-02-07 medium6.7 CVE-2023-6840 An issue has been discovered in GitLab EE affecting all versions from 16.4 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2 which allows a maint… gitlab · gitlab 2024-02-07 medium6.5 CVE-2023-6736 An issue has been discovered in GitLab EE affecting all versions starting from 11.3 before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions … gitlab · gitlab 2024-02-07 medium6.5 CVE-2023-6159 An issue has been discovered in GitLab CE/EE affecting all versions from 12.7 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1 It was possible f… gitlab · gitlab 2024-01-26 medium5.3 CVE-2023-5612 An issue has been discovered in GitLab affecting all versions before 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1. gitlab · gitlab 2024-01-26 medium4.3 CVE-2024-0456 An authorization vulnerability exists in GitLab versions 14.0 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1. gitlab · gitlab 2024-01-26 critical9.9 CVE-2024-0402 An issue has been discovered in GitLab CE/EE affecting all versions from 16.0 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1 which allows an a… gitlab · gitlab 2024-01-26 medium6.4 CVE-2023-5933 An issue has been discovered in GitLab CE/EE affecting all versions after 13.7 before 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1. gitlab · gitlab 2024-01-26 medium5.3 CVE-2024-23903 Non-constant time webhook token comparison in Jenkins GitLab Branch Source Plugin maven · io.jenkins.plugins:gitlab-branch-source 2024-01-24 medium4.3 CVE-2024-23902 CSRF vulnerability in Jenkins GitLab Branch Source Plugin maven · io.jenkins.plugins:gitlab-branch-source 2024-01-24 medium5.4 CVE-2024-23901 Shared projects are unconditionally discovered by Jenkins GitLab Branch Source Plugin maven · io.jenkins.plugins:gitlab-branch-source 2024-01-24 critical10.0 CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control VulnerabilityExploited gitlab · gitlab 2024-01-12 medium6.6 CVE-2023-6955 A missing authorization check vulnerability exists in GitLab Remote Development affecting all versions prior to 16.5.6, 16.6 prior to 16.6.4 and 16.7 prior to … gitlab · gitlab 2024-01-12 high7.3 CVE-2023-5356 Incorrect authorization checks in GitLab CE/EE from all versions starting from 8.13 before 16.5.6, all versions starting from 16.6 before 16.6.4, all versions … gitlab · gitlab 2024-01-12 high7.6 CVE-2023-4812 An issue has been discovered in GitLab EE affecting all versions starting from 15.3 before 16.5.6, all versions starting from 16.6 before 16.6.4, all versions … gitlab · gitlab 2024-01-12 low3.5 CVE-2023-2030 An issue has been discovered in GitLab CE/EE affecting all versions from 12.2 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which an attac… gitlab · gitlab 2024-01-12 high7.3 CVE-2023-6944 @backstage/backend-app-api leaks GitLab access tokens npm · @backstage/backend-app-api 2024-01-04 medium4.9 CVE-2023-3907 A privilege escalation vulnerability in GitLab EE affecting all versions from 16.0 prior to 16.4.4, 16.5 prior to 16.5.4, and 16.6 prior to 16.6.2 allows a pro… gitlab · gitlab 2023-12-17 high7.4 CVE-2023-6680 An improper certificate validation issue in Smartcard authentication in GitLab EE affecting all versions from 11.6 prior to 16.4.4, 16.5 prior to 16.5.4, and 1… gitlab · gitlab 2023-12-15 medium5.7 CVE-2023-6051 An issue has been discovered in GitLab CE/EE affecting all versions before 16.4.4, all versions starting from 16.5 before 16.5.4, all versions starting from 16… gitlab · gitlab 2023-12-15

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.