Puppet
Products by Puppet Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2024 there have been 0 vulnerabilities in Puppet . Last year Puppet had 5 security vulnerabilities published. Right now, Puppet is on track to have less security vulnerabilities in 2024 than it did last year.
Year | Vulnerabilities | Average Score |
---|---|---|
2024 | 0 | 0.00 |
2023 | 5 | 8.44 |
2022 | 3 | 9.47 |
2021 | 9 | 7.01 |
2020 | 3 | 7.23 |
2019 | 6 | 8.13 |
2018 | 14 | 7.30 |
It may take a day or so for new Puppet vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Puppet Security Vulnerabilities
Versions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw
CVE-2023-5309
9.8 - Critical
- November 07, 2023
Versions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw which results in broken session management for SAML implementations.
Session Fixation
In Puppet Bolt versions prior to 3.27.4
CVE-2023-5214
9.8 - Critical
- October 06, 2023
In Puppet Bolt versions prior to 3.27.4, a path to escalate privileges was identified.
Improper Privilege Management
For certificates that utilize the auto-renew feature in Puppet Server, a flaw exists which prevents the certificates
CVE-2023-5255
7.5 - High
- October 03, 2023
For certificates that utilize the auto-renew feature in Puppet Server, a flaw exists which prevents the certificates from being revoked.
Improper Resource Shutdown or Release
A privilege escalation
CVE-2023-2530
9.8 - Critical
- June 07, 2023
A privilege escalation allowing remote code execution was discovered in the orchestration service.
A Regular Expression Denial of Service (ReDoS) issue was discovered in Puppet Server 7.9.2 certificate validation
CVE-2023-1894
5.3 - Medium
- May 04, 2023
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.
ReDoS
Command injection is possible in the puppetlabs-mysql module prior to version 13.0.0
CVE-2022-3276
8.8 - High
- October 07, 2022
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 Enterprise.
Command injection is possible in the puppetlabs-apt module prior to version 9.0.0
CVE-2022-3275
9.8 - Critical
- October 07, 2022
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.
In certain situations it is possible for an unmanaged rule to exist on the target system
CVE-2022-0675
9.8 - Critical
- March 02, 2022
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.
Improper Input Validation
A flaw was discovered in Continuous Delivery for Puppet Enterprise (CD4PE)
CVE-2021-27024
8.1 - High
- November 18, 2021
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
A flaw was discovered in Puppet Agent and Puppet Server
CVE-2021-27023
9.8 - Critical
- November 18, 2021
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
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'.
CVE-2021-27025
6.5 - Medium
- November 18, 2021
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'.
A flaw was divered in Puppet Enterprise and other Puppet products where sensitive plan parameters may be logged
CVE-2021-27026
4.4 - Medium
- November 18, 2021
A flaw was divered in Puppet Enterprise and other Puppet products where sensitive plan parameters may be logged
Insertion of Sensitive Information into Log File
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
CVE-2021-27022
4.9 - Medium
- September 07, 2021
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).
Insertion of Sensitive Information into Log File
The mechanism which performs certificate validation was discovered to have a flaw
CVE-2021-27018
7.5 - High
- August 30, 2021
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 data source.
Improper Certificate Validation
PuppetDB logging included potentially sensitive system information.
CVE-2021-27019
4.3 - Medium
- August 30, 2021
PuppetDB logging included potentially sensitive system information.
Insertion of Sensitive Information into Log File
Puppet Enterprise presented a security risk by not sanitizing user input when doing a CSV export.
CVE-2021-27020
8.8 - High
- August 30, 2021
Puppet Enterprise presented a security risk by not sanitizing user input when doing a CSV export.
CSV Injection
A flaw was discovered in Puppet DB, this flaw results in an escalation of privileges which
CVE-2021-27021
8.8 - High
- July 20, 2021
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.
SQL Injection
In Continuous Delivery for Puppet Enterprise (CD4PE) before 3.4.0, changes to resources or classes containing Sensitive parameters
CVE-2020-7944
7.7 - High
- March 26, 2020
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.
Information Disclosure
Puppet Server and PuppetDB provide useful performance and debugging information via their metrics API endpoints
CVE-2020-7943
7.5 - High
- March 11, 2020
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 well as function names and class names. Previously, these endpoints were open to the local network. PE 2018.1.13 & 2019.5.0, Puppet Server 6.9.2 & 5.3.12, and PuppetDB 6.9.1 & 5.2.13 disable trapperkeeper-metrics /v1 metrics API and only allows /v2 access on localhost by default. This affects software versions: Puppet Enterprise 2018.1.x stream prior to 2018.1.13 Puppet Enterprise prior to 2019.5.0 Puppet Server prior to 6.9.2 Puppet Server prior to 5.3.12 PuppetDB prior to 6.9.1 PuppetDB prior to 5.2.13 Resolved in: Puppet Enterprise 2018.1.13 Puppet Enterprise 2019.5.0 Puppet Server 6.9.2 Puppet Server 5.3.12 PuppetDB 6.9.1 PuppetDB 5.2.13
Previously, Puppet operated on a model
CVE-2020-7942
6.5 - Medium
- February 19, 2020
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 be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19
Improper Certificate Validation
Previous versions of Puppet Agent didn't verify the peer in the SSL connection prior to downloading the CRL
CVE-2018-11751
5.4 - Medium
- December 16, 2019
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.
Improper Certificate Validation
mcollective has a default password set at install
CVE-2014-0175
9.8 - Critical
- December 13, 2019
mcollective has a default password set at install
Use of Hard-coded Credentials
When using the cd4pe::root_configuration task to configure a Continuous Delivery for PE installation
CVE-2019-10695
6.5 - Medium
- December 12, 2019
When using the cd4pe::root_configuration task to configure a Continuous Delivery for PE installation, the root users username and password were exposed in the jobs Job Details pane in the PE console. These issues have been resolved in version 1.2.1 of the puppetlabs/cd4pe module.
Insertion of Sensitive Information into Log File
The express install
CVE-2019-10694
9.8 - Critical
- December 12, 2019
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. If they do not use that URL, there is an overlooked default password for the admin user. This was resolved in Puppet Enterprise 2019.0.3 and 2018.1.9.
Use of Hard-coded Credentials
Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container
CVE-2018-11747
9.8 - Critical
- March 21, 2019
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.
Improper Certificate Validation
Prior to version 0.3.0
CVE-2018-6517
7.5 - High
- March 21, 2019
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.
Improper Certificate Validation
Previous releases of the Puppet cisco_ios module output SSH session debug information including login credentials to a world readable file on every run
CVE-2018-11752
5.5 - Medium
- October 02, 2018
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.
Insufficiently Protected Credentials
Previous releases of the Puppet cisco_ios module did not validate a host's identity before starting a SSH connection
CVE-2018-11750
6.5 - Medium
- October 02, 2018
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.
Improper Input Validation
Previous releases of the Puppet device_manager module creates configuration files containing credentials that are world readable
CVE-2018-11748
7.8 - High
- October 02, 2018
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.
Insufficiently Protected Credentials
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
CVE-2018-11749
9.8 - Critical
- August 24, 2018
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.
Cleartext Transmission of Sensitive Information
In Puppet Discovery prior to 1.2.0, when running Discovery against Windows hosts, WinRM connections
CVE-2018-11746
9.8 - Critical
- July 03, 2018
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.
Insufficiently Protected Credentials
The previous version of Puppet Enterprise 2018.1 is vulnerable to unsafe code execution when upgrading pe-razor-server
CVE-2018-6512
9.8 - Critical
- June 11, 2018
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.
Code Injection
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
CVE-2018-6513
8.8 - High
- June 11, 2018
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.
Untrusted Path
A cross-site scripting vulnerability in Puppet Enterprise Console of Puppet Enterprise
CVE-2018-6511
5.4 - Medium
- May 08, 2018
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.
XSS
A cross-site scripting vulnerability in Puppet Enterprise Console of Puppet Enterprise
CVE-2018-6510
5.4 - Medium
- May 08, 2018
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.
XSS
In previous versions of Puppet Agent it was possible for the agent to retrieve facts from an environment
CVE-2017-10690
6.5 - Medium
- February 09, 2018
In previous versions of Puppet Agent it was possible for the agent to retrieve facts from an environment that it was not classified to retrieve from. This was resolved in Puppet Agent 5.3.4, included in Puppet Enterprise 2017.3.4
Improper Privilege Management
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
CVE-2018-6508
8 - High
- February 09, 2018
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.
Use of Externally-Controlled Format String
Puppet Enterprise versions prior to 2016.4.5 and 2017.2.1 did not correctly authenticate users before returning labeled RBAC access tokens
CVE-2017-2297
7.5 - High
- February 01, 2018
Puppet Enterprise versions prior to 2016.4.5 and 2017.2.1 did not correctly authenticate users before returning labeled RBAC access tokens. This issue has been fixed in Puppet Enterprise 2016.4.5 and 2017.2.1. This only affects users with labeled tokens, which is not the default for tokens.
authentification
In Puppet Enterprise 2017.1.x and 2017.2.1
CVE-2017-2296
6.5 - Medium
- February 01, 2018
In Puppet Enterprise 2017.1.x and 2017.2.1, using specially formatted strings with certain formatting characters as Classifier node group names or RBAC role display names causes errors, effectively causing a DOS to the service. This was resolved in Puppet Enterprise 2017.2.2.
Improper Input Validation
Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 shipped with an MCollective configuration
CVE-2017-2293
4.9 - Medium
- February 01, 2018
Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 shipped with an MCollective configuration that allowed the package plugin to install or remove arbitrary packages on all managed agents. This release adds default configuration to not allow these actions. Customers who rely on this functionality can change this policy.
Puppet Enterprise 3.7.x and 3.8.0 might
CVE-2015-4100
6.8 - Medium
- December 21, 2017
Puppet Enterprise 3.7.x and 3.8.0 might allow remote authenticated users to manage certificates for arbitrary nodes by leveraging a client certificate trusted by the master, aka a "Certificate Authority Reverse Proxy Vulnerability."
Improper Certificate Validation
The console in Puppet Enterprise 3.7.x, 3.8.x, and 2015.2.x does not set the secure flag for the JSESSIONID cookie in an HTTPS session
CVE-2015-8470
6.5 - Medium
- December 11, 2017
The console in Puppet Enterprise 3.7.x, 3.8.x, and 2015.2.x does not set the secure flag for the JSESSIONID cookie in an HTTPS session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an HTTP session.
Information Disclosure
Cross-site scripting (XSS) vulnerability in the console in Puppet Enterprise before 2015.2.1
CVE-2015-6502
6.1 - Medium
- December 11, 2017
Cross-site scripting (XSS) vulnerability in the console in Puppet Enterprise before 2015.2.1 allows remote attackers to inject arbitrary web script or HTML via the string parameter, related to Login Redirect.
XSS
Puppet Enterprise 2015.3.3 and 2016.x before 2016.4.0, and Puppet Agent 1.3.6 through 1.7.0
CVE-2016-5714
7.2 - High
- October 18, 2017
Puppet Enterprise 2015.3.3 and 2016.x before 2016.4.0, and Puppet Agent 1.3.6 through 1.7.0 allow remote attackers to bypass a host whitelist protection mechanism and execute arbitrary code on Puppet nodes via vectors related to command validation, aka "Puppet Execution Protocol (PXP) Command Whitelist Validation Vulnerability."
Authorization
Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of potentially sensitive information triggered by specially crafted request.
CVE-2017-7529
7.5 - High
- July 13, 2017
Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of potentially sensitive information triggered by specially crafted request.
Integer Overflow or Wraparound
Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 failed to mark MCollective server private keys as sensitive (a feature added in Puppet 4.6)
CVE-2017-2294
7.5 - High
- July 05, 2017
Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 failed to mark MCollective server private keys as sensitive (a feature added in Puppet 4.6), so key values could be logged and stored in PuppetDB. These releases use the sensitive data type to ensure this won't happen anymore.
Information Disclosure
The mcollective-sshkey-security plugin before 0.5.1 for Puppet uses a server-specified identifier as part of a path where a file is written
CVE-2017-2298
6.5 - Medium
- June 30, 2017
The mcollective-sshkey-security plugin before 0.5.1 for Puppet uses a server-specified identifier as part of a path where a file is written. A compromised server could use this to write a file to an arbitrary location on the client with the filename appended with the string "_pub.pem".
Improper Input Validation
MCollective 2.7.0 and 2.8.x before 2.8.9, as used in Puppet Enterprise
CVE-2016-2788
9.8 - Critical
- February 13, 2017
MCollective 2.7.0 and 2.8.x before 2.8.9, as used in Puppet Enterprise, allows remote attackers to execute arbitrary code via vectors related to the mco ping command.
Authorization
Open redirect vulnerability in the Console in Puppet Enterprise before 2015.2.1
CVE-2015-6501
6.1 - Medium
- January 12, 2017
Open redirect vulnerability in the Console in Puppet Enterprise before 2015.2.1 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via the string parameter.
Open Redirect
Open redirect vulnerability in the Console in Puppet Enterprise 2015.x and 2016.x before 2016.4.0
CVE-2016-5715
6.1 - Medium
- January 12, 2017
Open redirect vulnerability in the Console in Puppet Enterprise 2015.x and 2016.x before 2016.4.0 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a // (slash slash) followed by a domain in the redirect parameter. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-6501.
Open Redirect
The pxp-agent component in Puppet Enterprise 2015.3.x before 2015.3.3 and Puppet Agent 1.3.x before 1.3.6 does not properly validate server certificates, which might
CVE-2016-2786
9.8 - Critical
- June 10, 2016
The pxp-agent component in Puppet Enterprise 2015.3.x before 2015.3.3 and Puppet Agent 1.3.x before 1.3.6 does not properly validate server certificates, which might allow remote attackers to spoof brokers and execute arbitrary commands via a crafted certificate.
Improper Input Validation
Puppet Server before 2.3.2 and Ruby puppetmaster in Puppet 4.x before 4.4.2 and in Puppet Agent before 1.4.2 might
CVE-2016-2785
9.8 - Critical
- June 10, 2016
Puppet Server before 2.3.2 and Ruby puppetmaster in Puppet 4.x before 4.4.2 and in Puppet Agent before 1.4.2 might allow remote attackers to bypass intended auth.conf access restrictions by leveraging incorrect URL decoding.
Authorization
Puppet Enterprise 2015.3 before 2015.3.1
CVE-2015-7330
8.8 - High
- April 11, 2016
Puppet Enterprise 2015.3 before 2015.3.1 allows remote attackers to bypass a host whitelist protection mechanism by leveraging the Puppet communications protocol.
7PK - Security Features
Puppet before 3.3.3 and 3.4 before 3.4.1 and Puppet Enterprise (PE) before 2.8.4 and 3.1 before 3.1.1
CVE-2013-4969
- January 07, 2014
Puppet before 3.3.3 and 3.4 before 3.4.1 and Puppet Enterprise (PE) before 2.8.4 and 3.1 before 3.1.1 allows local users to overwrite arbitrary files via a symlink attack on unspecified files.
insecure temporary file
The (1) template and (2) inline_template functions in the master server 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
CVE-2013-1640
- March 20, 2013
The (1) template and (2) inline_template functions in the master server 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 users to execute arbitrary code via a crafted catalog request.
lib/puppet/network/authstore.rb in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might
CVE-2012-3408
- August 06, 2012
lib/puppet/network/authstore.rb in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might allow remote attackers to spoof an agent by acquiring a previously used IP address.
authentification
Puppet 2.6.x before 2.6.15 and 2.7.x before 2.7.13, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x, and 2.5.x before 2.5.1
CVE-2012-1988
- May 29, 2012
Puppet 2.6.x before 2.6.15 and 2.7.x before 2.7.13, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x, and 2.5.x before 2.5.1 allows remote authenticated users with agent SSL keys and file-creation permissions on the puppet master to execute arbitrary commands by creating a file whose full pathname contains shell metacharacters, then performing a filebucket request.
Shell injection