Skip to navigation

Security Advisory Important: puppet security update

Advisory: RHSA-2013:0710-1
Type: Security Advisory
Severity: Important
Issued on: 2013-04-04
Last updated on: 2013-04-04
Affected Products: Red Hat OpenStack Folsom
CVEs (cve.mitre.org): CVE-2012-6120
CVE-2013-1640
CVE-2013-1652
CVE-2013-1654
CVE-2013-2274
CVE-2013-2275

Details

Updated puppet packages that fix several security issues are now available
for Red Hat OpenStack Folsom.

The Red Hat Security Response Team has rated this update as having
important security impact. Common Vulnerability Scoring System (CVSS) base
scores, which give detailed severity ratings, are available for each
vulnerability from the CVE links in the References section.

Puppet allows provisioning, patching, and configuration of clients to be
managed and automated.

A flaw was found in how Puppet handled certain HTTP PUT requests. An
attacker with valid authentication credentials, and authorized to save to
the authenticated client's own report, could construct a malicious request
that could possibly cause the Puppet master to execute arbitrary code.
(CVE-2013-2274)

A flaw was found in how Puppet handled the "template" and "inline_template"
functions during catalog compilation. If an authenticated attacker were to
requests its catalog from the Puppet master, it could possibly result in
arbitrary code execution when the catalog is compiled. (CVE-2013-1640)

A flaw was found in how Puppet handled certain HTTP GET requests. An
attacker with valid authentication credentials could construct a request to
retrieve catalogs from the Puppet master that they are not authorized to
access. (CVE-2013-1652)

It was found that the default /etc/puppet/auth.conf configuration file
allowed an authenticated node to submit a report for any other node, which
could breach compliance requirements. (CVE-2013-2275)

It was found that the /var/log/puppet directory was created world-readable.
This could allow local users to obtain sensitive information from the
Puppet log files. (CVE-2012-6120)

It was found that Puppet allowed the use of the SSLv2 protocol. A Puppet
agent could use this to negotiate the use of the weak SSLv2 protocol for
its connection to a Puppet master. (CVE-2013-1654)

Red Hat would like to thank Puppet Labs for reporting CVE-2013-1640,
CVE-2013-1652, CVE-2013-1654, CVE-2013-2274, and CVE-2013-2275.

Note: In most default configurations these issues are not directly
exploitable unless the attacker has access to the underlying OpenStack
infrastructure (e.g. shell access to a Nova compute node).

Users of Red Hat OpenStack Folsom are advised to upgrade to these updated
packages, which upgrade Puppet to version 2.6.18 and correct these issues.


Solution

Before applying this update, make sure all previously-released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/knowledge/articles/11258

Updated packages

Red Hat OpenStack Folsom

SRPMS:
puppet-2.6.18-1.el6ost.src.rpm     MD5: c411a5ef6624c765f277f43e9df91753
SHA-256: c84751d2f7b51eb974753af0c23ceaed9c950f32e9af489d5b5c47d7b8a6ef2c
 
x86_64:
puppet-2.6.18-1.el6ost.noarch.rpm     MD5: 36f7250d0f7b49858cf895dccf63b275
SHA-256: 42fbbb1b518059930f76d22e19ce0c3752a698a2e3be722ebc84c04314b828d4
puppet-server-2.6.18-1.el6ost.noarch.rpm     MD5: 0ff2b15bf920c6dd234b71dd3ea194a7
SHA-256: ad84a726d5dded20ec7955c98395ce691744f86b1279d757e99be19ceaea628f
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

908629 - CVE-2012-6120 Puppet: Directory /var/log/puppet is world readable
919770 - CVE-2013-1654 Puppet: SSL protocol downgrade
919773 - CVE-2013-2274 Puppet: HTTP PUT report saving code execution vulnerability
919783 - CVE-2013-1640 Puppet: catalog request code execution
919784 - CVE-2013-1652 Puppet: HTTP GET request catalog retrieval
919785 - CVE-2013-2275 Puppet: default auth.conf allows authenticated node to submit a report for any other node


References



These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/