Puppet: Multiple vulnerabilities
1.
Gentoo Linux Security Advisory
Version Information
| Advisory Reference |
GLSA 201208-02 / Puppet |
| Release Date |
August 14, 2012 |
| Latest Revision |
August 14, 2012: 1 |
| Impact |
high |
| Exploitable |
local |
| Package |
Vulnerable versions |
Unaffected versions |
Architecture(s) |
| app-admin/puppet |
<
2.7.13 |
>=
2.7.13 |
All supported architectures
|
Related bugreports:
#410857
Synopsis
Multiple vulnerabilities have been found in Puppet, the worst of
which could lead to execution of arbitrary code.
2.
Impact Information
Background
Puppet is a system configuration management tool written in Ruby.
Description
Multiple vulnerabilities have been found in Puppet:
- Puppet uses predictable file names for temporary files
(CVE-2012-1906).
- REST requests for a file in a remote filebucket are not handled
properly by overriding filebucket storage locations (CVE-2012-1986).
- REST requests for a file in a remote filebucket are not handled
properly by reading streams or writing files on the Puppet master's
file system (CVE-2012-1987).
- File name paths are not properly sanitized from bucket requests
(CVE-2012-1988).
- The Telnet utility in Puppet does not handle temporary files securely
(CVE-2012-1989).
Impact
A local attacker with access to agent SSL keys could possibly execute
arbitrary code with the privileges of the process, cause a Denial of
Service condition, or perform symlink attacks to overwrite or read
arbitrary files on the Puppet master.
3.
Resolution Information
Workaround
There is no known workaround at this time.
Resolution
All Puppet users should upgrade to the latest version:
Code Listing 3.1: Resolution |
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-admin/puppet-2.7.13"
|
4.
References
|
