NetSight

Security Dashboard

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

Reset
1,002 matching advisories · page 25 of 34Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2020-13346 Membership changes are not reflected in ToDo subscriptions in GitLab versions prior to 13.2.10, 13.3.7 and 13.4.2, allowing guest users to access confidential … gitlab · gitlab 2020-10-07 medium4.3 CVE-2020-13335 Improper group membership validation when deleting a user account in GitLab >=7.12 allows a user to delete own account without deleting/transferring their grou… gitlab · gitlab 2020-10-07 medium5.9 CVE-2020-13334 In GitLab versions prior to 13.2.10, 13.3.7 and 13.4.2, improper authorization checks allow a non-member of a project/group to change the confidentiality attri… gitlab · gitlab 2020-10-07 medium5.5 CVE-2020-13345 An issue has been discovered in GitLab affecting all versions starting from 10.8. gitlab · gitlab 2020-10-06 medium4.3 CVE-2020-13333 A potential DOS vulnerability was discovered in GitLab versions 13.1, 13.2 and 13.3. gitlab · gitlab 2020-10-06 medium5.4 CVE-2020-13338 An issue has been discovered in GitLab affecting versions prior to 12.10.13, 13.0.8, 13.1.2. gitlab · gitlab 2020-10-02 medium4.0 CVE-2020-13336 An issue has been discovered in GitLab affecting versions from 11.8 before 12.10.13. gitlab · gitlab 2020-09-30 medium5.4 CVE-2020-13331 An issue has been discovered in GitLab affecting versions prior to 12.10.13. gitlab · gitlab 2020-09-30 medium4.4 CVE-2020-13330 An issue has been discovered in GitLab affecting versions prior to 12.10.13. gitlab · gitlab 2020-09-30 medium6.5 CVE-2020-13329 An issue has been discovered in GitLab affecting versions from 12.6.2 prior to 12.10.13. gitlab · gitlab 2020-09-30 medium4.8 CVE-2020-13328 An issue has been discovered in GitLab affecting versions prior to 13.1.2, 13.0.8 and 12.10.13. gitlab · gitlab 2020-09-30 medium4.3 CVE-2020-13326 A vulnerability was discovered in GitLab versions prior to 13.1. gitlab · gitlab 2020-09-30 medium6.5 CVE-2020-13324 A vulnerability was discovered in GitLab versions prior to 13.1. gitlab · gitlab 2020-09-30 medium6.5 CVE-2020-13320 An issue has been discovered in GitLab before version 12.10.13 that allowed a project member with limited permissions to view the project security dashboard. gitlab · gitlab 2020-09-30 medium4.3 CVE-2020-13319 An issue has been discovered in GitLab affecting versions prior to 13.1.2, 13.0.8 and 12.10.13. gitlab · gitlab 2020-09-30 medium6.5 CVE-2020-13296 An issue has been discovered in GitLab affecting versions >=10.7 <13.0.14, >=13.1.0 <13.1.8, >=13.2.0 <13.2.6. gitlab · gitlab 2020-09-30 medium6.5 CVE-2020-13310 A vulnerability was discovered in GitLab runner versions before 13.1.3, 13.2.3 and 13.3.1. gitlab · gitlab 2020-09-14 medium5.4 CVE-2020-13309 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium5.5 CVE-2020-13301 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.5 CVE-2020-13317 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8, and 13.3.4. gitlab · gitlab 2020-09-14 medium4.3 CVE-2020-13313 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.5 CVE-2020-13312 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium4.3 CVE-2020-13311 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.4 CVE-2020-13318 A vulnerability was discovered in GitLab versions before 13.0.12, 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium5.4 CVE-2020-13316 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium5.4 CVE-2020-13289 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium4.3 CVE-2020-13287 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.5 CVE-2020-13284 A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. gitlab · gitlab 2020-09-14 medium6.4 CVE-2020-13286 For GitLab before 13.0.12, 13.1.6, 13.2.3 user controlled git configuration settings can be modified to result in Server Side Request Forgery. gitlab · gitlab 2020-08-13 medium6.5 CVE-2020-13281 For GitLab before 13.0.12, 13.1.6, 13.2.3 a denial of service exists in the project import feature gitlab · gitlab 2020-08-13

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.