NetSight

Security Dashboard

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

Reset
1,646 matching advisories · page 37 of 55Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2021-22250 Improper authorization in GitLab CE/EE affecting all versions since 13.3 allowed users to view and delete impersonation tokens that administrators created for … gitlab · gitlab 2021-08-25 medium4.3 CVE-2021-22247 Improper authorization in GitLab CE/EE affecting all versions since 13.0 allows guests in private projects to view CI/CD analytics gitlab · gitlab 2021-08-25 low2.7 CVE-2021-22245 Improper validation of commit author in GitLab CE/EE affecting all versions allowed an attacker to make several pages in a project impossible to view gitlab · gitlab 2021-08-25 low3.1 CVE-2021-22244 Improper authorization in the vulnerability report feature in GitLab EE affecting all versions since 13.1 allowed a reporter to access vulnerability data gitlab · gitlab 2021-08-25 medium5.0 CVE-2021-22243 Under specialized conditions, GitLab CE/EE versions starting 7.10 may allow existing GitLab users to use an invite URL meant for another email address to gain … gitlab · gitlab 2021-08-25 high8.7 CVE-2021-22242 Insufficient input sanitization in Mermaid markdown in GitLab CE/EE version 11.4 and up allows an attacker to exploit a stored cross-site scripting vulnerabili… gitlab · gitlab 2021-08-25 medium6.6 CVE-2021-22237 Under specialized conditions, GitLab may allow a user with an impersonation token to perform Git actions even if impersonation is disabled. gitlab · gitlab 2021-08-25 medium5.5 CVE-2021-22236 Due to improper handling of OAuth client IDs, new subscriptions generated OAuth tokens on an incorrect OAuth client application. gitlab · gitlab 2021-08-25 medium4.9 CVE-2021-22253 Improper authorization in GitLab EE affecting all versions since 13.4 allowed a user who previously had the necessary access to trigger deployments to protecte… gitlab · gitlab 2021-08-23 medium6.5 CVE-2021-22252 A confusion between tag and branch names in GitLab CE/EE affecting all versions since 13.7 allowed a Developer to access protected CI variables which should on… gitlab · gitlab 2021-08-23 medium4.3 CVE-2021-22251 Improper validation of invited users' email address in GitLab EE affecting all versions since 12.2 allowed projects to add members with email address domain th… gitlab · gitlab 2021-08-23 medium4.3 CVE-2021-22249 A verbose error message in GitLab EE affecting all versions since 12.2 could disclose the private email address of a user invited to a group gitlab · gitlab 2021-08-23 medium5.3 CVE-2021-22248 Improper authorization on the pipelines page in GitLab CE/EE affecting all versions since 13.12 allowed unauthorized users to view some pipeline information fo… gitlab · gitlab 2021-08-23 low3.1 CVE-2021-22254 Under very specific conditions a user could be impersonated using Gitlab shell. gitlab · gitlab 2021-08-20 high7.7 CVE-2021-22246 A vulnerability was discovered in GitLab versions before 14.0.2, 13.12.6, 13.11.6. gitlab · gitlab 2021-08-20 medium6.8 CVE-2021-22238 An issue has been discovered in GitLab affecting all versions starting with 13.3. gitlab · gitlab 2021-08-20 critical9.6 CVE-2021-22234 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.11 before 13.11.7, all versions starting from 13.12 before 13.12.8, and al… gitlab · gitlab 2021-08-05 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 medium4.2 CVE-2021-22240 Improper access control in GitLab EE versions 13.11.6, 13.12.6, and 14.0.2 allows users to be created via single sign on despite user cap being enabled gitlab · gitlab 2021-08-05 medium4.3 CVE-2021-22233 An information disclosure vulnerability in GitLab EE versions 13.10 and later allowed a user to read project details gitlab · gitlab 2021-07-07 medium4.7 CVE-2021-22225 Insufficient input sanitization in markdown in GitLab version 13.11 and up allows an attacker to exploit a stored cross-site scripting vulnerability via a spec… gitlab · gitlab 2021-07-07 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 low3.5 CVE-2021-22231 A denial of service in user's profile page is found starting with GitLab CE/EE 8.0 that allows attacker to reject access to their profile page via using a spec… gitlab · gitlab 2021-07-07 medium4.9 CVE-2021-22230 Improper code rendering while rendering merge requests could be exploited to submit malicious code. gitlab · gitlab 2021-07-07 medium6.1 CVE-2021-22227 A reflected cross-site script vulnerability in GitLab before versions 13.11.6, 13.12.6 and 14.0.2 allowed an attacker to send a malicious link to a victim and … gitlab · gitlab 2021-07-07 medium6.5 CVE-2021-22228 An issue has been discovered in GitLab affecting all versions before 13.11.6, all versions starting from 13.12 before 13.12.6, and all versions starting from 1… gitlab · gitlab 2021-07-06 medium6.1 CVE-2021-22223 Client-Side code injection through Feature Flag name in GitLab CE/EE starting with 11.9 allows a specially crafted feature flag name to PUT requests on behalf … gitlab · gitlab 2021-07-06 low3.5 CVE-2021-22232 HTML injection was possible via the full name field before versions 13.11.6, 13.12.6, and 14.0.2 in GitLab CE gitlab · gitlab 2021-07-06 medium5.9 CVE-2021-22229 An issue has been discovered in GitLab CE/EE affecting all versions starting with 12.8. gitlab · gitlab 2021-07-06 medium6.5 CVE-2021-22226 Under certain conditions, some users were able to push to protected branches that were restricted to deploy keys in GitLab CE/EE since version 13.9 gitlab · gitlab 2021-07-06

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.