Puppet Enterprise 2.8.2

Puppet Enterprise 2.8.x before 2.8.7 allows remote attackers to obtain sensitive information via vectors involving hiding and unhiding nodes.

Published: 2014-06-17T14:00:00.000Z
Updated: 2024-08-06T10:35:57.139Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-09-17T00:11:37.416Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-09-17T01:50:33.558Z

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.

Published: 2014-03-14T16:00:00.000Z
Updated: 2024-08-06T16:59:41.266Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-09-17T01:11:25.432Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-09-16T17:24:19.504Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-09-16T18:33:35.806Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-09-16T16:54:14.003Z

The dashboard report in Puppet Enterprise before 3.0.1 allows attackers to execute arbitrary YAML code via a crafted report-specific type.

Published: 2013-10-25T23:00:00.000Z
Updated: 2024-08-06T16:59:41.043Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-08-06T16:59:40.991Z

Open redirect vulnerability in the login page in Puppet Enterprise before 3.0.1 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the service parameter.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-09-17T00:26:05.296Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-09-16T21:09:07.716Z

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.

Published: 2013-08-20T22:00:00.000Z
Updated: 2024-08-06T16:52:26.979Z