Puppet vulnerabilities
130 vulnerabilities
Known vulnerabilities in Puppet products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 42 products.
Products
42- Puppet Enterprise89 vulnerabilities
- Puppet42 vulnerabilities
- Puppet Agent12 vulnerabilities
- Puppet Server8 vulnerabilities
- Continuous Delivery4 vulnerabilities
- Marionette Collective3 vulnerabilities
- Puppetdb3 vulnerabilities
- Puppetlabs Mysql3 vulnerabilities
- Bolt2 vulnerabilities
- Discovery2 vulnerabilities
- Facter2 vulnerabilities
- Mcollective2 vulnerabilities
- Puppet Discovery2 vulnerabilities
- Chloride1 vulnerabilities
- Cisco Ios1 vulnerabilities
- Cisco Ios Module1 vulnerabilities
- Device Manager1 vulnerabilities
- Firewall1 vulnerabilities
- Firewall Module1 vulnerabilities
- Hiera1 vulnerabilities
- Mcollective, Puppet, Puppet Enterprise1 vulnerabilities
- Mcollective Puppet Agent1 vulnerabilities
- Mcollective Puppet Agent Plugin1 vulnerabilities
- Mcollective Sshkey Security1 vulnerabilities
- Pe Client Tools1 vulnerabilities
- Pe Razor Server1 vulnerabilities
- Peadm Forge Module1 vulnerabilities
- Puppet Connect1 vulnerabilities
- Puppet Dashboard1 vulnerabilities
- Puppet Enterprise 2018.1.X Prior To 2018.1.1, Razor Server And Pe Razor Server Prior To 1.9.0.01 vulnerabilities
- Puppet Enterprise And Puppet Agent1 vulnerabilities
- Puppet Enterprise Client Tools1 vulnerabilities
- Puppetlabs Apache1 vulnerabilities
- Puppetlabs Apt1 vulnerabilities
- Puppetlabs/Apache1 vulnerabilities
- Puppetlabs/Apt1 vulnerabilities
- Puppetlabs/Facter Task1 vulnerabilities
- Puppetlabs/Mysql1 vulnerabilities
- Puppetlabs/Puppet Conf1 vulnerabilities
- Razor Server1 vulnerabilities
- Remediate1 vulnerabilities
- Stdlib1 vulnerabilities
CVE-2018-11749puppetpuppet_enterprise
EPSS score0.76%
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. This affects Puppet Enterprise 2018.1.3, 2017.3.9, and 2016.4.14, and is fixed in Puppet Enterprise 2018.1.4, 2017.3.10, and 2016.4.15. It scored an 8.5 CVSS score.CVE-2018-11746puppetdiscovery+1EPSS score1.38%
In Puppet Discovery prior to 1.2.0, when running Discovery against Windows hosts, WinRM connections can fall back to using basic auth over insecure channels if a HTTPS server is not available. This can expose the login credentials being used by Puppet Discovery.CVE-2018-11752puppetcisco_iosEPSS score0.27%
Previous releases of the Puppet cisco_ios module output SSH session debug information including login credentials to a world readable file on every run. These issues have been resolved in the 0.4.0 release.CVE-2018-11750puppetcisco_ios_moduleEPSS score1.07%
Previous releases of the Puppet cisco_ios module did not validate a host's identity before starting a SSH connection. As of the 0.4.0 release of cisco_ios, host key checking is enabled by default.CVE-2018-11751puppetpuppet_serverEPSS score0.61%
Previous versions of Puppet Agent didn't verify the peer in the SSL connection prior to downloading the CRL. This issue is resolved in Puppet Agent 6.4.0.CVE-2018-11747puppetdiscovery+1EPSS score0.72%
Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container. In version 1.4.0, a unique certificate will be generated on installation or the user will be able to provide their own TLS certificate for ingress.CVE-2018-11748puppetdevice_managerEPSS score0.28%
Previous releases of the Puppet device_manager module creates configuration files containing credentials that are world readable. This issue has been resolved as of device_manager 2.7.0.CVE-2018-6516puppetpe-client-tools+1EPSS score0.85%
On Windows only, with a specifically crafted configuration file an attacker could get Puppet PE client tools (aka pe-client-tools) 16.4.x prior to 16.4.6, 17.3.x prior to 17.3.6, and 18.1.x prior to 18.1.2 to load arbitrary code with privilege escalation.CVE-2018-6515puppetpuppet+1EPSS score0.85%
Puppet Agent 1.10.x prior to 1.10.13, Puppet Agent 5.3.x prior to 5.3.7, and Puppet Agent 5.5.x prior to 5.5.2 on Windows only, with a specially crafted configuration file an attacker could get pxp-agent to load arbitrary code with privilege escalation.CVE-2018-6511puppetpuppet_enterpriseEPSS score0.64%
A cross-site scripting vulnerability in Puppet Enterprise Console of Puppet Enterprise allows a user to inject scripts into the Puppet Enterprise Console when using the Puppet Enterprise Console. Affected releases are Puppet Puppet Enterprise: 2017.3.x versions prior to 2017.3.6.CVE-2018-6508debianpuppet-module-puppetlabs-apache+11EPSS score1.87%
Puppet Enterprise 2017.3.x prior to 2017.3.3 are vulnerable to a remote execution bug when a specially crafted string was passed into the facter_task or puppet_conf tasks. This vulnerability only affects tasks in the affected modules, if you are not using puppet tasks you are not affected by this vulnerability.CVE-2018-6514puppetpuppet+1EPSS score0.85%
In Puppet Agent 1.10.x prior to 1.10.13, Puppet Agent 5.3.x prior to 5.3.7, Puppet Agent 5.5.x prior to 5.5.2, Facter on Windows is vulnerable to a DLL preloading attack, which could lead to a privilege escalation.CVE-2018-6513puppetpuppet+2EPSS score1.12%
Puppet Enterprise 2016.4.x prior to 2016.4.12, Puppet Enterprise 2017.3.x prior to 2017.3.7, Puppet Enterprise 2018.1.x prior to 2018.1.1, Puppet Agent 1.10.x prior to 1.10.13, Puppet Agent 5.3.x prior to 5.3.7, and Puppet Agent 5.5.x prior to 5.5.2, were vulnerable to an attack where an unprivileged user on Windows agents could write custom facts that can escalate privileges on the next puppet run. This was possible through the loading of shared libraries from untrusted paths.CVE-2018-6517RubyGemschloride+1EPSS score0.89%
Prior to version 0.3.0, chloride's use of net-ssh resulted in host fingerprints for previously unknown hosts getting added to the user's known_hosts file without confirmation. In version 0.3.0 this is updated so that the user's known_hosts file is not updated by chloride.CVE-2018-6510puppetpuppet_enterpriseEPSS score0.51%
A cross-site scripting vulnerability in Puppet Enterprise Console of Puppet Enterprise allows a user to inject scripts into the Puppet Enterprise Console when using the Orchestrator. Affected releases are Puppet Puppet Enterprise: 2017.3.x versions prior to 2017.3.6.CVE-2018-6512puppetpe-razor-server+3EPSS score1.94%
The previous version of Puppet Enterprise 2018.1 is vulnerable to unsafe code execution when upgrading pe-razor-server. Affected releases are Puppet Enterprise: 2018.1.x versions prior to 2018.1.1 and razor-server and pe-razor-server prior to 1.9.0.0.CVE-2013-2275canonicalubuntu_linux+4EPSS score2.91%
The default configuration for puppet masters 0.25.0 and later in Puppet before 2.6.18, 2.7.x before 2.7.21, and 3.1.x before 3.1.1, and Puppet Enterprise before 1.2.7 and 2.7.x before 2.7.2, allows remote authenticated nodes to submit reports for other nodes via unspecified vectors.CVE-2013-2716puppetpuppet_enterprise+1EPSS score1.32%
Puppet Labs Puppet Enterprise before 2.8.0 does not use a "randomized secret" in the CAS client config file (cas_client_config.yml) when upgrading from older 1.2.x or 2.0.x versions, which allows remote attackers to obtain console access via a crafted cookie.CVE-2013-2274debianpuppet+3EPSS score2.91%
Puppet 2.6.x before 2.6.18 and Puppet Enterprise 1.2.x before 1.2.7 allows remote authenticated users to execute arbitrary code on the puppet master, or an agent with puppet kick enabled, via a crafted request for a report.CVE-2013-1654canonicalubuntu_linux+4EPSS score2.95%
Puppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, and Puppet Enterprise 2.7.x before 2.7.2, does not properly negotiate the SSL protocol between client and master, which allows remote attackers to conduct SSLv2 downgrade attacks against SSLv3 sessions via unspecified vectors.