p PatchFirst

PatchFirst · Latest vulnerabilities

puppet vulnerabilities

Vulnerabilities published for puppet in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 40

  1. CVE-2020-7942

    Medium · CVSS 6.5EPSS 0.8%No fix published

    CVE-2020-7942

    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 n

    Published Updated
  2. CVE-2016-5713

    Critical · CVSS 9.8EPSS 2.02%Fix available

    CVE-2016-5713

    Versions of Puppet Agent prior to 1.6.0 included a version of the Puppet Execution Protocol (PXP) agent that passed environment variables through to Puppet runs. This could allow unauthorized code to be loaded. This bug was first introduced in Puppet Agent 1.3.0.

    • Update to 4.7.0-1
    Published Updated
  3. CVE-2016-5714

    High · CVSS 7.2EPSS 2.24%Fix available

    CVE-2016-5714

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

    • Update to 4.8.0-1
    Published Updated
  4. CVE-2017-2295

    High · CVSS 8.2EPSS 2.76%Fix available

    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 data on the wire to PSON or safely decoded YAML.

    • Update to 4.8.2-5
    Published Updated
  5. CVE-2013-4956

    Not ratedEPSS 0.38%Fix available

    CVE-2013-4956

    Puppet Module Tool (PMT), as used in Puppet 2.7.x before 2.7.23 and 3.2.x before 3.2.4, and Puppet Enterprise 2.8.x before 2.8.3 and 3.0.x before 3.0.1, installs modules with weak permissions if those permissions were used when the modules were originally built, which might allow local users to read or modify those modules depending on the original permissions.

    • Update to 3.2.4-1
    Published Updated
  6. CVE-2013-4761

    Not ratedEPSS 1.64%Fix available

    CVE-2013-4761

    Unspecified vulnerability in Puppet 2.7.x before 2.7.23 and 3.2.x before 3.2.4, and Puppet Enterprise 2.8.x before 2.8.3 and 3.0.x before 3.0.1, allows remote attackers to execute arbitrary Ruby programs from the master via the resource_type service. NOTE: this vulnerability can only be exploited utilizing unspecified "local file system access" to the Puppet Master.

    • Update to 3.2.4-1
    Published Updated
  7. CVE-2013-1653

    Not ratedEPSS 5.38%Fix available

    CVE-2013-1653

    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, when listening for incoming connections is enabled and allowing access to the "run" REST endpoint is allowed, allows remote authenticated users to execute arbitrary code via a crafted HTTP request.

    • Update to 2.7.18-3
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →