2385 matches found
puppet-naivesigning NSE Script
Detects if naive signing is enabled on a Puppet server. This enables attackers to create any Certificate Signing Request and have it signed, allowing them to impersonate as a puppet agent. This can leak the configuration of the agents as well as any other sensitive information found in the...
CVE-2017-2292
Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safeload, allowing the potential for arbitrary code execution on the server. The fix for this is to call YAML.safeload on input. This has been tested in all Puppet-supplied MCollective plugins, but there is a...
Puppet Enterprise 2017.1.0 - 2017.2.1 DoS Vulnerability
Puppet Enterprise is prone to a denial of service DoS vulnerability. SPDX-FileCopyrightText: 2017 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only CPE =...
Puppet Enterprise < 2016.4.5, 2016.5.x < 2017.2.1 Multiple Vulnerabilities
Puppet Enterprise is prone to multiple vulnerabilities. SPDX-FileCopyrightText: 2017 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only CPE = "cpe:/a:puppet:enterprise"; if...
Deserialization of untrusted data
Versions of Puppet prior to 4.10.1 will deserialize data off the wire from the agent to the server, in this case with a attacker-specified format. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constrains the format of...
CVE-2017-2294
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...
CVE-2017-2294
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...
CVE-2017-2294
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...
CVE-2017-2295
Versions of Puppet prior to 4.10.1 will deserialize data off the wire from the agent to the server, in this case with a attacker-specified format. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constrains the format of...
Code injection
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...
DEBIAN-CVE-2017-2295
Versions of Puppet prior to 4.10.1 will deserialize data off the wire from the agent to the server, in this case with a attacker-specified format. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constrains the format of...
CVE-2017-2295
Versions of Puppet prior to 4.10.1 will deserialize data off the wire from the agent to the server, in this case with a attacker-specified format. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constrains the format of...
CVE-2017-2294
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...
CVE-2017-2295
Versions of Puppet prior to 4.10.1 will deserialize data off the wire from the agent to the server, in this case with a attacker-specified format. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constrains the format of...
CVE-2017-2294
CVE-2017-2294 affects Puppet Enterprise prior to 2016.4.5 or 2017.2.1, where MCollective server private keys were not marked as sensitive, allowing key values to be logged or stored in PuppetDB. The underlying issue is the absence of the sensitive data type for these keys, leading to potential in...
CVE-2017-2295
CVE-2017-2295 affects Puppet prior to 4.10.1, where deserializing data off the wire could be forced into an attacker-controlled format, enabling remote code execution. The underlying issue is unsafe YAML deserialization; the fix constrains on-wire data formats to PSON or safely decoded YAML (and ...
CVE-2017-2295
Versions of Puppet prior to 4.10.1 will deserialize data off the wire from the agent to the server, in this case with a attacker-specified format. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constrains the format of...
CVE-2017-2294
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...
