NetSight

Security Dashboard

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

Reset
95 matching advisories · page 3 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.6 CVE-2020-13292 In GitLab before 13.0.12, 13.1.6 and 13.2.3, it is possible to bypass E-mail verification which is required for OAuth Flow. gitlab · gitlab 2020-08-10 critical9.8 CVE-2020-10980 GitLab EE/CE 8.0.rc1 to 12.9 is vulnerable to a blind SSRF in the FogBugz integration. gitlab · gitlab 2020-04-08 critical9.8 CVE-2020-10956 GitLab 8.10 and later through 12.9 is vulnerable to an SSRF in a project import note feature. gitlab · gitlab 2020-03-27 critical9.8 CVE-2020-10077 GitLab EE 3.0 through 12.8.1 allows SSRF. gitlab · gitlab 2020-03-13 critical9.8 CVE-2020-10074 GitLab 10.1 through 12.8.1 has Incorrect Access Control. gitlab · gitlab 2020-03-13 critical9.1 CVE-2020-10083 GitLab 12.7 through 12.8.1 has Insecure Permissions. gitlab · gitlab 2020-03-13 critical9.8 CVE-2019-12443 An issue was discovered in GitLab Community and Enterprise Edition 10.2 through 11.11. gitlab · gitlab 2020-03-10 critical9.8 CVE-2019-12428 An issue was discovered in GitLab Community and Enterprise Edition 6.8 through 11.11. gitlab · gitlab 2020-03-10 critical9.8 CVE-2020-8113 GitLab 10.7 and later through 12.7.2 has Incorrect Access Control. gitlab · gitlab 2020-03-06 critical9.8 CVE-2020-8114 GitLab EE 8.9 and later through 12.7.2 has Insecure Permission gitlab · gitlab 2020-02-05 critical9.8 CVE-2019-5464 A flawed DNS rebinding protection issue was discovered in GitLab CE/EE 10.2 and later in the `url_blocker.rb` which could result in SSRF where the library is u… gitlab · gitlab 2020-01-28 critical9.8 CVE-2019-15585 Improper authentication exists in < 12.3.2, < 12.2.6, and < 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE) in the GitLab SAML integratio… gitlab · gitlab 2020-01-28 critical9.8 CVE-2019-19628 In GitLab EE 11.3 through 12.5.3, 12.4.5, and 12.3.8, insufficient parameter sanitization for the Maven package registry could lead to privilege escalation and… gitlab · gitlab 2020-01-05 critical9.8 CVE-2019-19088 Gitlab Enterprise Edition (EE) 11.3 through 12.4.2 allows Directory Traversal. gitlab · gitlab 2020-01-03 critical9.8 CVE-2019-15741 An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. gitlab · omnibus 2019-09-16 critical10.0 CVE-2019-5485 NPM package gitlabhook version 0.0.17 is vulnerable to a Command Injection vulnerability. npm · gitlabhook 2019-09-13 critical9.8 CVE-2019-6960 An issue was discovered in GitLab Community and Enterprise Edition 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. gitlab · gitlab 2019-09-09 critical9.8 CVE-2019-14943 An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.1.4. gitlab · gitlab 2019-08-29 critical9.8 CVE-2019-9732 An issue was discovered in GitLab Community and Enterprise Edition 10.x (starting from 10.8) and 11.x before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 1… gitlab · gitlab 2019-05-29 critical9.8 CVE-2019-9485 An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. gitlab · gitlab 2019-05-29 critical9.8 CVE-2019-9218 An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. gitlab · gitlab 2019-05-29 critical9.1 CVE-2019-7353 An Incorrect Access Control issue was discovered in GitLab Community and Enterprise Edition 11.7.x before 11.7.4. gitlab · gitlab 2019-05-17 critical9.1 CVE-2019-5883 An Incorrect Access Control issue was discovered in GitLab Community and Enterprise Edition 6.0 and later but before 11.3.11, 11.4.x before 11.4.8, and 11.5.x … gitlab · gitlab 2019-05-17 critical9.1 CVE-2019-9890 An issue was discovered in GitLab Community and Enterprise Edition 10.x and 11.x before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. gitlab · gitlab 2019-04-17 critical9.8 CVE-2019-9756 An issue was discovered in GitLab Community and Enterprise Edition 10.x (starting from 10.8) and 11.x before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 1… gitlab · gitlab 2019-04-17 critical9.8 CVE-2019-9217 An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. gitlab · gitlab 2019-04-17 critical10.0 CVE-2019-9174 An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. gitlab · gitlab 2019-04-17 critical10.0 CVE-2018-18843 The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4.4 has SSRF. gitlab · gitlab 2018-12-04 critical9.8 CVE-2018-18641 An issue was discovered in GitLab Community and Enterprise Edition before 11.2.7, 11.3.x before 11.3.8, and 11.4.x before 11.4.3. gitlab · gitlab 2018-12-04 critical9.8 CVE-2018-18649 An issue was discovered in the wiki API in GitLab Community and Enterprise Edition before 11.2.7, 11.3.x before 11.3.8, and 11.4.x before 11.4.3. gitlab · gitlab 2018-11-29

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.