NetSight

Security Dashboard

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

Reset
98 matching advisories · page 3 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-6wqm-j54p-485j Malware in puppeteercluserMalware npm · puppeteercluser 2024-11-05 critical GHSA-v6q6-qqjf-qfqx Malware in puppeteer-harrMalware npm · puppeteer-harr 2024-11-05 critical GHSA-qm66-2g48-fc6f Malware in puppeteer-extra-plugin-adblokcerMalware npm · puppeteer-extra-plugin-adblokcer 2024-11-05 critical GHSA-945w-v793-9gwf Malware in puppeteer-captreMalware npm · puppeteer-captre 2024-11-04 critical GHSA-q68v-hmpr-8hqc Malware in puppeteer-html2pdMalware npm · puppeteer-html2pd 2024-11-04 critical GHSA-r5m7-6p5v-x2hh Malware in puppeteer-firfoxMalware npm · puppeteer-firfox 2024-11-04 critical GHSA-3jv6-3cq7-h6mh Malware in puppeteercapturMalware npm · puppeteercaptur 2024-11-04 critical GHSA-9jq2-5297-x2xq Malware in puppeteer-autoscrollMalware npm · puppeteer-autoscroll 2024-11-04 critical GHSA-x2pw-rwcc-5552 Malware in puppeteer-req-interceptorMalware npm · puppeteer-req-interceptor 2024-11-04 critical GHSA-3rrg-cqgg-cfwm Malware in puppeteer-screencorderMalware npm · puppeteer-screencorder 2024-11-04 critical GHSA-rp2q-wq4m-gvg4 Malware in puppeteerrecordrMalware npm · puppeteerrecordr 2024-11-04 critical GHSA-cjg8-mc5j-63fv Malware in puppeteer-extra-stealthMalware npm · puppeteer-extra-stealth 2024-11-04 critical GHSA-m6rx-v2cf-4c4m Malware in puppeteerpluginstealthMalware npm · puppeteerpluginstealth 2024-11-04 critical9.8 CVE-2024-7923 An authentication bypass vulnerability has been identified in Pulpcore when deployed with Gunicorn versions prior to 22.0, due to the puppet-pulpcore configura… redhat · satellite 2024-09-04 critical9.8 CVE-2024-7012 An authentication bypass vulnerability has been identified in Foreman when deployed with External Authentication, due to the puppet-foreman configuration. redhat · satellite 2024-09-04 critical9.8 CVE-2023-5214 In Puppet Bolt versions prior to 3.27.4, a path to escalate privileges was identified. rubygems · bolt 2023-10-06 critical GHSA-jj3h-qhcq-8m97 Malware in puppeteer-exampleMalware npm · puppeteer-example 2023-09-20 critical9.8 CVE-2023-2530 A privilege escalation allowing remote code execution was discovered in the orchestration service. puppet · puppet_enterprise 2023-06-07 critical GHSA-vr78-c3wp-prfc Malware in puppetlabs-stdlibMalware npm · puppetlabs-stdlib 2022-06-20 critical GHSA-56cm-q3ch-985c Malware in karma-puppeteer-clientMalware npm · karma-puppeteer-client 2022-06-20 critical9.8 CVE-2021-27023 A flaw was discovered in Puppet Agent and Puppet Server that may result in a leak of HTTP credentials when following HTTP redirects to a different host. rubygems · puppet 2021-11-18 critical9.8 CVE-2014-0175 mcollective has a default password set at install puppet · marionette_collective, redhat · openshift, debian · debian_linux 2019-12-13 critical9.8 CVE-2019-10694 The express install, which is the suggested way to install Puppet Enterprise, gives the user a URL at the end of the install to set the admin password. puppet · puppet_enterprise 2019-12-12 critical9.9 CVE-2019-10458 Jenkins Puppet Enterprise Pipeline 1.3.1 and earlier specifies unsafe values in its custom Script Security whitelist, allowing attackers able to execute Script… maven · org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline 2019-10-16 critical9.8 CVE-2018-11747 Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container. puppet · discovery 2019-03-21 critical9.8 CVE-2018-11749 When users are configured to use startTLS with RBAC LDAP, at login time, the user's credentials are sent via plaintext to the LDAP server. puppet · puppet_enterprise 2018-08-24 critical9.8 CVE-2018-6512 The previous version of Puppet Enterprise 2018.1 is vulnerable to unsafe code execution when upgrading pe-razor-server. puppet · pe-razor-server, puppet · puppet_enterprise, puppet · razor-server 2018-06-11 critical9.8 CVE-2015-7224 puppetlabs-mysql 3.1.0 through 3.6.0 allow remote attackers to bypass authentication by leveraging creation of a database account without a password when a 'my… puppet · puppetlabs-mysql 2017-12-21 critical9.8 CVE-2016-5713 Versions of Puppet Agent prior to 1.6.0 included a version of the Puppet Execution Protocol (PXP) agent that passed environment variables through to Puppet run… puppet · puppet_agent 2017-12-06 critical9.0 CVE-2017-2292 Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safe_load, allowing the potential for arbitrary code execution on the ser… puppet · mcollective 2017-06-30

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.