Puppet: Multiple vulnerabilities
Multiple vulnerabilities have been found in Puppet, the worst of
which could lead to execution of arbitrary code.
Puppet
August 14, 2012
August 14, 2012: 1
410857
local
2.7.13
2.7.13
Puppet is a system configuration management tool written in Ruby.
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).
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.
There is no known workaround at this time.
All Puppet users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-admin/puppet-2.7.13"
CVE-2012-1906
CVE-2012-1986
CVE-2012-1987
CVE-2012-1988
CVE-2012-1989
ackle
ackle