NetSight

Security Dashboard

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

Reset
1,002 matching advisories · page 30 of 34Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2019-15577 An information disclosure vulnerability exists in GitLab CE/EE <v12.3.2, <v12.2.6, and <v12.1.12 that allowed project milestones to be disclosed via groups bro… gitlab · gitlab 2019-12-18 medium5.3 CVE-2019-18456 An issue was discovered in GitLab Community and Enterprise Edition 8.17 through 12.4 in the Search feature provided by Elasticsearch integration.. gitlab · gitlab 2019-11-26 medium6.1 CVE-2019-18454 An issue was discovered in GitLab Community and Enterprise Edition 10.5 through 12.4 in link validation for RDoc wiki pages feature. gitlab · gitlab 2019-11-26 medium4.3 CVE-2019-18453 An issue was discovered in GitLab Community and Enterprise Edition 11.6 through 12.4 in the add comments via email feature. gitlab · gitlab 2019-11-26 medium5.3 CVE-2019-18452 An issue was discovered in GitLab Community and Enterprise Edition 11.3 through 12.4 when moving an issue to a public project from a private one. gitlab · gitlab 2019-11-26 medium6.1 CVE-2019-18451 An issue was discovered in GitLab Community and Enterprise Edition 10.7.4 through 12.4 in the InternalRedirect filtering feature. gitlab · gitlab 2019-11-26 medium4.3 CVE-2019-18450 An issue was discovered in GitLab Community and Enterprise Edition before 12.4 in the Project labels feature. gitlab · gitlab 2019-11-26 medium4.3 CVE-2019-18449 An issue was discovered in GitLab Community and Enterprise Edition before 12.4 in the autocomplete feature. gitlab · gitlab 2019-11-26 medium6.5 CVE-2019-18448 An issue was discovered in GitLab Community and Enterprise Edition before 12.4. gitlab · gitlab 2019-11-26 medium4.3 CVE-2019-18447 An issue was discovered in GitLab Community and Enterprise Edition before 12.4. gitlab · gitlab 2019-11-26 medium4.3 CVE-2019-18446 An issue was discovered in GitLab Community and Enterprise Edition 8.15 through 12.4. gitlab · gitlab 2019-11-26 medium5.3 CVE-2019-18459 An issue was discovered in GitLab Community and Enterprise Edition 11.3 to 12.3 in the protected environments feature. gitlab · gitlab 2019-11-26 medium4.3 CVE-2019-18463 An issue was discovered in GitLab Community and Enterprise Edition through 12.4. gitlab · gitlab 2019-11-26 medium4.3 CVE-2019-18462 An issue was discovered in GitLab Community and Enterprise Edition 11.3 through 12.4. gitlab · gitlab 2019-11-26 medium4.3 CVE-2019-18461 An issue was discovered in GitLab Community and Enterprise Edition 11.3 through 12.3 when a sub group epic is added to a public group. gitlab · gitlab 2019-11-26 medium6.5 CVE-2019-15593 GitLab 12.2.3 contains a security vulnerability that allows a user to affect the availability of the service through a Denial of Service attack in Issue Commen… gitlab · gitlab 2019-11-22 medium5.5 CVE-2019-10429 Jenkins GitLab Logo Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access … maven · org.jenkins-ci.plugins:gitlab-logo 2019-09-25 medium6.5 CVE-2019-10416 Jenkins Violation Comments to GitLab Plugin 2.28 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could be v… maven · org.jenkins-ci.plugins:violation-comments-to-gitlab 2019-09-25 medium6.5 CVE-2019-10415 Jenkins Violation Comments to GitLab Plugin 2.28 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they c… maven · org.jenkins-ci.plugins:violation-comments-to-gitlab 2019-09-25 medium5.3 CVE-2019-15740 An issue was discovered in GitLab Community and Enterprise Edition 7.9 through 12.2.1. gitlab · gitlab 2019-09-16 medium6.1 CVE-2019-15739 An issue was discovered in GitLab Community and Enterprise Edition 8.1 through 12.2.1. gitlab · gitlab 2019-09-16 medium5.3 CVE-2019-15738 An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.2.1. gitlab · gitlab 2019-09-16 medium6.5 CVE-2019-15737 An issue was discovered in GitLab Community and Enterprise Edition through 12.2.1. gitlab · gitlab 2019-09-16 medium4.3 CVE-2019-15734 An issue was discovered in GitLab Community and Enterprise Edition 8.6 through 12.2.1. gitlab · gitlab 2019-09-16 medium4.3 CVE-2019-15733 An issue was discovered in GitLab Community and Enterprise Edition 7.12 through 12.2.1. gitlab · gitlab 2019-09-16 medium5.3 CVE-2019-15732 An issue was discovered in GitLab Community and Enterprise Edition 12.2 through 12.2.1. gitlab · gitlab 2019-09-16 medium5.3 CVE-2019-15731 An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.2.1. gitlab · gitlab 2019-09-16 medium5.3 CVE-2019-15727 An issue was discovered in GitLab Community and Enterprise Edition 11.2 through 12.2.1. gitlab · gitlab 2019-09-16 medium5.3 CVE-2019-15726 An issue was discovered in GitLab Community and Enterprise Edition through 12.2.1. gitlab · gitlab 2019-09-16 medium6.1 CVE-2019-15724 An issue was discovered in GitLab Community and Enterprise Edition 11.10 through 12.2.1. gitlab · gitlab 2019-09-16

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.