Puppet vulnerabilities, page 2

130 vulnerabilities

Known vulnerabilities in Puppet products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 42 products.

8.5CVE-2013-1398puppetpuppet_enterprise+1
EPSS score
1.54%
The pe_mcollective module in Puppet Enterprise (PE) before 2.7.1 does not properly restrict access to a catalog of private SSL keys, which allows remote authenticated users to obtain sensitive information and gain privileges by leveraging root access to a node, related to the master role.
6.8CVE-2013-1399puppetpuppet_enterprise+1
EPSS score
0.60%
Multiple cross-site request forgery (CSRF) vulnerabilities in the (1) node request management, (2) live management, and (3) user administration components in the console in Puppet Enterprise (PE) before 2.7.1 allow remote attackers to hijack the authentication of unspecified victims via unknown vectors.
7.5CVE-2013-1655debianpuppet+4
EPSS score
4.56%
Puppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, when running Ruby 1.9.3 or later, allows remote attackers to execute arbitrary code via vectors related to "serialized attributes."
9CVE-2013-1640canonicalubuntu_linux+3
EPSS score
4.93%
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.
4.9CVE-2013-1652canonicalubuntu_linux+4
EPSS score
1.86%
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.
7.1CVE-2013-1653canonicalubuntu_linux+4
EPSS score
5.38%
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.
5.8CVE-2013-4762puppetpuppet_enterprise
EPSS score
1.64%
Puppet Enterprise before 3.0.1 does not sufficiently invalidate a session when a user logs out, which might allow remote attackers to hijack sessions by obtaining an old session ID.
2.1CVE-2013-4969canonicalubuntu_linux+6
EPSS score
0.43%
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.
5CVE-2013-4964puppetpuppet_enterprise
EPSS score
1.62%
Puppet Enterprise before 3.0.1 does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.
6.9CVE-2013-4958puppetpuppet_enterprise
EPSS score
0.38%
Puppet Enterprise before 3.0.1 does not use a session timeout, which makes it easier for attackers to gain privileges by leveraging an unattended workstation.
5CVE-2013-4967puppetpuppet_enterprise
EPSS score
1.27%
Puppet Enterprise before 3.0.1 allows remote attackers to obtain the database password via vectors related to how the password is "seeded as a console parameter," External Node Classifiers, and the lack of access control for /nodes.
5.8CVE-2013-4962puppetpuppet_enterprise
EPSS score
1.23%
The reset password page in Puppet Enterprise before 3.0.1 does not force entry of the current password, which allows attackers to modify user passwords by leveraging session hijacking, an unattended workstation, or other vectors.
6.8CVE-2013-4957puppetpuppet_enterprise
EPSS score
1.12%
The dashboard report in Puppet Enterprise before 3.0.1 allows attackers to execute arbitrary YAML code via a crafted report-specific type.
2.1CVE-2013-4959puppetpuppet_enterprise
EPSS score
0.35%
Puppet Enterprise before 3.0.1 uses HTTP responses that contain sensitive information without the "no-cache" setting, which might allow local users to obtain sensitive information such as (1) host name, (2) MAC address, and (3) SSH keys via the web browser cache.
6.4CVE-2013-4966puppetpuppet_enterprise
EPSS score
1.08%
The master external node classification script in Puppet Enterprise before 3.2.0 does not verify the identity of consoles, which allows remote attackers to create arbitrary classifications on the master by spoofing a console.
3.6CVE-2013-4956debianpuppet+3
EPSS score
0.38%
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.
5CVE-2013-4965puppetpuppet_enterprise
EPSS score
1.32%
Puppet Enterprise before 3.1.0 does not properly restrict the number of authentication attempts by a console account, which makes it easier for remote attackers to bypass intended access restrictions via a brute-force attack.
5CVE-2013-4961puppetpuppet_enterprise
EPSS score
1.80%
Puppet Enterprise before 3.0.1 includes version information for the Apache and Phusion Passenger products in its HTTP response headers, which allows remote attackers to obtain sensitive information.
6.1CVE-2013-4968puppetpuppet_enterprise
EPSS score
0.82%
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."
6.8CVE-2013-4963puppetpuppet_enterprise
EPSS score
0.83%
Multiple cross-site request forgery (CSRF) vulnerabilities in Puppet Enterprise (PE) before 3.0.1 allow remote attackers to hijack the authentication of users for requests that deleting a (1) report, (2) group, or (3) class or possibly have other unspecified impact.