p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de puppet

Vulnerabilidades publicadas para puppet en los últimos 30 días: 0. Incluidas en el catálogo KEV: 0.

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 40

  1. CVE-2020-7942

    Media · CVSS 6.5EPSS 0,8%Sin corrección publicada

    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

    Publicación Actualización
  2. CVE-2014-3250

    Media · CVSS 6.5EPSS 0,89%Corrección disponible

    CVE-2014-3250

    The default vhost configuration file in Puppet before 3.6.2 does not include the SSLCARevocationCheck directive, which might allow remote attackers to obtain sensitive information via a revoked certificate when a Puppet master runs with Apache 2.4.

    • Actualiza a 3.7.0-1
    Publicación Actualización
  3. CVE-2016-5713

    Crítica · CVSS 9.8EPSS 2,02%Corrección disponible

    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.

    • Actualiza a 4.7.0-1
    Publicación Actualización
  4. CVE-2016-5714

    Alta · CVSS 7.2EPSS 2,24%Corrección disponible

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

    • Actualiza a 4.8.0-1
    Publicación Actualización
  5. CVE-2017-2295

    Alta · CVSS 8.2EPSS 2,76%Corrección disponible

    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.

    • Actualiza a 4.8.2-5
    Publicación Actualización
  6. CVE-2013-4956

    Sin evaluarEPSS 0,38%Corrección disponible

    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.

    • Actualiza a 3.2.4-1
    Publicación Actualización
  7. CVE-2013-4761

    Sin evaluarEPSS 1,64%Corrección disponible

    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.

    • Actualiza a 3.2.4-1
    Publicación Actualización
  8. CVE-2012-6120

    Sin evaluarEPSS 0,39%Corrección disponible

    CVE-2012-6120

    Red Hat OpenStack Essex and Folsom creates the /var/log/puppet directory with world-readable permissions, which allows local users to obtain sensitive information such as Puppet log files.

    • Actualiza a 2.6.4-2
    Publicación Actualización
  9. CVE-2013-2275

    Sin evaluarEPSS 2,91%Corrección disponible

    CVE-2013-2275

    The default configuration for puppet masters 0.25.0 and later 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 nodes to submit reports for other nodes via unspecified vectors.

    • Actualiza a 2.7.18-3
    Publicación Actualización
  10. CVE-2013-1654

    Sin evaluarEPSS 2,95%Corrección disponible

    CVE-2013-1654

    Puppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, and Puppet Enterprise 2.7.x before 2.7.2, does not properly negotiate the SSL protocol between client and master, which allows remote attackers to conduct SSLv2 downgrade attacks against SSLv3 sessions via unspecified vectors.

    • Actualiza a 2.7.18-3
    Publicación Actualización
  11. CVE-2013-1653

    Sin evaluarEPSS 5,38%Corrección disponible

    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.

    • Actualiza a 2.7.18-3
    Publicación Actualización
  12. CVE-2013-1652

    Sin evaluarEPSS 1,86%Corrección disponible

    CVE-2013-1652

    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 with a valid certificate and private key to read arbitrary catalogs or poison the master's cache via unspecified vectors.

    • Actualiza a 2.7.18-3
    Publicación Actualización

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →