NetSight

Security Dashboard

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

Reset
1,002 matching advisories · page 23 of 34Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 medium3.7 CVE-2021-32823 Potential Denial-of-Service in bindata rubygems · bindata 2021-06-23 medium6.8 CVE-2021-22175 GitLab Server-Side Request Forgery (SSRF) VulnerabilityExploited gitlab · gitlab 2021-06-11 medium6.1 CVE-2021-22220 An issue has been discovered in GitLab affecting all versions starting with 13.10. gitlab · gitlab 2021-06-08 medium6.5 CVE-2021-22216 A denial of service vulnerability in all versions of GitLab CE/EE before 13.12.2, 13.11.5 or 13.10.5 allows an attacker to cause uncontrolled resource consumpt… gitlab · gitlab 2021-06-08 medium6.5 CVE-2021-22221 An issue has been discovered in GitLab affecting all versions starting from 12.9.0 before 13.10.5, all versions starting from 13.11.0 before 13.11.5, all versi… gitlab · gitlab 2021-06-08 medium4.4 CVE-2021-22219 All versions of GitLab CE/EE starting from 9.5 before 13.10.5, all versions starting from 13.11 before 13.11.5, and all versions starting from 13.12 before 13.… gitlab · gitlab 2021-06-08 medium6.5 CVE-2021-22217 A denial of service vulnerability in all versions of GitLab CE/EE before 13.12.2, 13.11.5 or 13.10.5 allows an attacker to cause uncontrolled resource consumpt… gitlab · gitlab 2021-06-08 medium6.8 CVE-2021-22214 When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab CE/EE affecting all versions starting fro… gitlab · gitlab 2021-06-08 medium5.3 CVE-2021-22210 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.2. gitlab · gitlab 2021-05-06 medium4.3 CVE-2021-22208 An issue has been discovered in GitLab affecting versions starting with 13.5 up to 13.9.7. gitlab · gitlab 2021-05-06 medium6.8 CVE-2021-22206 An issue has been discovered in GitLab affecting all versions starting from 11.6. gitlab · gitlab 2021-05-06 medium5.9 CVE-2021-22200 An issue has been discovered in GitLab CE/EE affecting all versions starting with 12.6. gitlab · gitlab 2021-04-02 medium4.3 CVE-2021-22198 An issue has been discovered in GitLab CE/EE affecting all versions from 13.8 and above allowing an authenticated user to delete incident metric images of publ… gitlab · gitlab 2021-04-02 medium6.3 CVE-2021-22196 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4. gitlab · gitlab 2021-04-02 medium4.3 CVE-2021-22177 Potential DoS was identified in gitlab-shell in GitLab CE/EE version 12.6.0 or above, which allows an attacker to spike the server resource utilization via git… gitlab · gitlab 2021-04-01 medium5.5 CVE-2021-21411 OAuth2-Proxy's `--gitlab-group` GitLab Group Authorization config flag stopped working in v7.0.0 go · github.com/oauth2-proxy/oauth2-proxy/v7 2021-03-26 medium5.7 CVE-2021-22194 In all versions of GitLab, marshalled session keys were being stored in Redis. gitlab · gitlab 2021-03-26 medium6.2 CVE-2021-22184 An information disclosure issue in GitLab starting from version 12.8 allowed a user with access to the server logs to see sensitive information that wasn't pro… gitlab · gitlab 2021-03-26 medium4.3 CVE-2021-22180 An issue has been discovered in GitLab affecting all versions starting from 13.4. gitlab · gitlab 2021-03-26 medium4.3 CVE-2021-22172 Improper authorization in GitLab 12.8+ allows a guest user in a private project to view tag data that should be inaccessible on the releases page gitlab · gitlab 2021-03-26 medium4.3 CVE-2021-22169 An issue was identified in GitLab EE 13.4 or later which leaked internal IP address via error messages. gitlab · gitlab 2021-03-24 medium4.9 CVE-2021-22186 An authorization issue in GitLab CE/EE version 9.4 and up allowed a group maintainer to modify group CI/CD variables which should be restricted to group owners gitlab · gitlab 2021-03-24 medium5.4 CVE-2021-22185 Insufficient input sanitization in wikis in GitLab version 13.8 and up allows an attacker to exploit a stored cross-site scripting vulnerability via a speciall… gitlab · gitlab 2021-03-24 medium5.4 CVE-2021-22179 A vulnerability was discovered in GitLab versions before 12.2. gitlab · gitlab 2021-03-24

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.