MediumCVSS 5.4
In versions of the PEADM Forge Module prior to 3.24.0 a security misconfiguration was discovered.
Vendor
puppet vulnerabilities
129 published CVES affecting puppet, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 129
- Critical
- 18
- High
- 30
- Medium
- 66
- Low
- 15
- Unscored
- 0
- CISA KEV
- 0
Products
- puppet enterprise 88
- puppet 42
- puppet agent 8
- puppet server 7
- continuous delivery 4
- marionette collective 3
- puppetdb 3
- puppetlabs-mysql 3
- Bolt 2
- discovery 2
- facter 2
- chloride 1
- cisco ios 1
- cisco ios module 1
- device manager 1
- firewall 1
- Firewall Module 1
- hiera 1
- mcollective 1
- mcollective-puppet-agent 1
- mcollective-sshkey-security 1
- pe-razor-server 1
- PEADM Forge Module 1
- puppet connect 1
- puppet dashboard 1
- puppet enterprise client tools 1
- puppetlabs-apache 1
- puppetlabs-apt 1
- razor-server 1
- remediate 1
Latest puppet CVEs
Newest publication first · page 1 of 6
-
-
CriticalCVSS 9.8
Versions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw which results in broken session management for SAML implementations.
-
CriticalCVSS 9.8
In Puppet Bolt versions prior to 3.27.4, a path to escalate privileges was identified.
-
HighCVSS 7.5
For certificates that utilize the auto-renew feature in Puppet Server, a flaw exists which prevents the certificates from being revoked.
-
CriticalCVSS 9.8
A privilege escalation allowing remote code execution was discovered in the orchestration service.
-
MediumCVSS 5.3
A Regular Expression Denial of Service (ReDoS) issue was discovered in Puppet Server 7.9.2 certificate validation. An issue related to specifically crafted certificate names significantly slowed down server operations.
-
HighCVSS 8.8
Command injection is possible in the puppetlabs-mysql module prior to version 13.0.0. A malicious actor is able to exploit this vulnerability only if they are able to provide unsanitized input to the module. This condition is rare in most deployments of Puppet and Puppet Enterpri...
-
CriticalCVSS 9.8
Command injection is possible in the puppetlabs-apt module prior to version 9.0.0. A malicious actor is able to exploit this vulnerability only if they are able to provide unsanitized input to the module. This condition is rare in most deployments of Puppet and Puppet Enterprise.
-
LowCVSS 3.5
Puppet Bolt prior to version 3.24.0 will print sensitive parameters when planning a run resulting in them potentially being logged when run programmatically, such as via Puppet Enterprise.
-
CriticalCVSS 9.8
In certain situations it is possible for an unmanaged rule to exist on the target system that has the same comment as the rule specified in the manifest. This could allow for unmanaged rules to exist on the target system and leave the system in an unsafe state.
-
MediumCVSS 4.4
A flaw was divered in Puppet Enterprise and other Puppet products where sensitive plan parameters may be logged
-
HighCVSS 8.1
A flaw was discovered in Continuous Delivery for Puppet Enterprise (CD4PE) that results in a user with lower privileges being able to access a Puppet Enterprise API token. This issue is resolved in CD4PE 4.10.0
-
CriticalCVSS 9.8 PoC
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. This is similar to CVE-2018-1000007
-
MediumCVSS 6.5 PoC
A flaw was discovered in Puppet Agent where the agent may silently ignore Augeas settings or may be vulnerable to a Denial of Service condition prior to the first 'pluginsync'.
-
MediumCVSS 4.9
A flaw was discovered in bolt-server and ace where running a task with sensitive parameters results in those sensitive parameters being logged when they should not be. This issue only affects SSH/WinRM nodes (inventory service nodes).
-
HighCVSS 8.8
Puppet Enterprise presented a security risk by not sanitizing user input when doing a CSV export.
-
HighCVSS 7.5
The mechanism which performs certificate validation was discovered to have a flaw that resulted in certificates signed by an internal certificate authority to not be properly validated. This issue only affects clients that are configured to utilize Tenable.sc as the vulnerability...
-
MediumCVSS 4.3
PuppetDB logging included potentially sensitive system information.
-
HighCVSS 8.8
A flaw was discovered in Puppet DB, this flaw results in an escalation of privileges which allows the user to delete tables via an SQL query.
-
MediumCVSS 5.5
Local registry credentials were included directly in the CD4PE deployment definition, which could expose these credentials to users who should not have access to them. This is resolved in Continuous Delivery for Puppet Enterprise 4.0.1.
-
HighCVSS 7.7
In Continuous Delivery for Puppet Enterprise (CD4PE) before 3.4.0, changes to resources or classes containing Sensitive parameters can result in the Sensitive parameters ending up in the impact analysis report.
-
HighCVSS 7.5
Puppet Server and PuppetDB provide useful performance and debugging information via their metrics API endpoints. For PuppetDB this may contain things like hostnames. Puppet Server reports resource names and titles for defined types (which may contain sensitive information) as wel...
-
HighCVSS 8.8
Parts of the Puppet Enterprise Console 3.x were found to be susceptible to clickjacking and CSRF (Cross-Site Request Forgery) attacks. This would allow an attacker to redirect user input to an untrusted site or hijack a user session.
-
MediumCVSS 6.5 PoC
Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the default node, the catalog can b...
-
MediumCVSS 5.4
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.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.