VYPR

Puppet Enterprise

by Puppet (software)

Source repositories

CVEs (92)

  • CVE-2017-2294HigJul 5, 2017
    risk 0.49cvss 7.5epss 0.01

    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…

  • CVE-2016-5714HigOct 18, 2017
    risk 0.47cvss 7.2epss 0.02

    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…

  • CVE-2025-10360MedSep 24, 2025
    risk 0.45cvss epss 0.00

    In Puppet Enterprise versions 2025.4.0 and 2025.5, the encryption key used for encrypting content in the Infra Assistant database was not excluded from the files gathered by Puppet backup. The key is only present on the system if the user has a Puppet Enterprise Advanced license…

  • CVE-2023-5309MedNov 7, 2023
    risk 0.44cvss 6.8epss 0.01

    Versions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw which results in broken session management for SAML implementations.

  • CVE-2015-4100MedDec 21, 2017
    risk 0.44cvss 6.8epss 0.01

    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."

  • CVE-2021-27025MedNov 18, 2021
    risk 0.42cvss 6.5epss 0.01

    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-2017-10690MedFeb 9, 2018
    risk 0.42cvss 6.5epss 0.01

    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

  • CVE-2017-2296MedFeb 1, 2018
    risk 0.42cvss 6.5epss 0.01

    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.

  • CVE-2015-8470MedDec 11, 2017
    risk 0.42cvss 6.5epss 0.02

    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.

  • CVE-2013-4968MedDec 11, 2019
    risk 0.40cvss 6.1epss 0.01

    Puppet Enterprise before 3.0.1 allows remote attackers to (1) conduct clickjacking attacks via unspecified vectors related to the console, and (2) conduct cross-site scripting (XSS) attacks via unspecified vectors related to "live management."

  • CVE-2015-6502MedDec 11, 2017
    risk 0.40cvss 6.1epss 0.01

    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.

  • CVE-2016-5715MedJan 12, 2017
    risk 0.40cvss 6.1epss 0.01

    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…

  • CVE-2015-6501MedJan 12, 2017
    risk 0.40cvss 6.1epss 0.01

    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.

  • CVE-2015-1855MedNov 29, 2019
    risk 0.39cvss 5.9epss 0.03

    verify_certificate_identity in the OpenSSL extension in Ruby before 2.0.0 patchlevel 645, 2.1.x before 2.1.6, and 2.2.x before 2.2.2 does not properly validate hostnames, which allows remote attackers to spoof servers via vectors related to (1) multiple wildcards, (1) wildcards…

  • CVE-2018-6511MedMay 8, 2018
    risk 0.35cvss 5.4epss 0.01

    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-6510MedMay 8, 2018
    risk 0.35cvss 5.4epss 0.01

    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-2016-9686MedFeb 8, 2017
    risk 0.35cvss 5.3epss 0.01

    The Puppet Communications Protocol (PCP) Broker incorrectly validates message header sizes. An attacker could use this to crash the PCP Broker, preventing commands from being sent to agents. This is resolved in Puppet Enterprise 2016.4.3 and 2016.5.2.

  • CVE-2023-1894MedMay 4, 2023
    risk 0.34cvss 5.3epss 0.00

    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.

  • CVE-2016-2787MedFeb 13, 2017
    risk 0.34cvss 5.3epss 0.01

    The Puppet Communications Protocol in Puppet Enterprise 2015.3.x before 2015.3.3 does not properly validate certificates for the broker node, which allows remote non-whitelisted hosts to prevent runs from triggering via unspecified vectors.

  • CVE-2021-27022MedSep 7, 2021
    risk 0.32cvss 4.9epss 0.01

    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).

Page 2 of 5