bugtraq - [SECURITY] [DSA 2643-1] puppet security update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Tue, 12 Mar 2013 23:48:19 +0100 (CET)
From: Yves-Alexis Perez <corsac@...ian.org>
To: bugtraq@...urityfocus.com
Subject: [SECURITY] [DSA 2643-1] puppet security update

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- -------------------------------------------------------------------------
Debian Security Advisory DSA-2643-1                   security@...ian.org
http://www.debian.org/security/                         Yves-Alexis Perez
March 12, 2013                         http://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : puppet
Vulnerability  : several
Problem type   : remote
Debian-specific: no
CVE ID         : CVE-2013-1640 CVE-2013-1652 CVE-2013-1653 CVE-2013-1654
                 CVE-2013-1655 CVE-2013-2274 CVE-2013-2275
Debian Bug     :

Multiple vulnerabilities were discovered in Puppet, a centralized
configuration management system.

CVE-2013-1640

    An authenticated malicious client may request its catalog from the puppet
    master, and cause the puppet master to execute arbitrary code. The puppet
    master must be made to invoke the `template` or `inline_template` functions
    during catalog compilation.

CVE-2013-1652

    An authenticated malicious client may retrieve catalogs from the puppet
    master that it is not authorized to access. Given a valid certificate and
    private key, it is possible to construct an HTTP GET request that will
    return a catalog for an arbitrary client.

CVE-2013-1653

    An authenticated malicious client may execute arbitrary code on Puppet
    agents that accept kick connections. Puppet agents are not vulnerable in
    their default configuration. However, if the Puppet agent is configured to
    listen for incoming connections, e.g. listen = true, and the agent's
    auth.conf allows access to the `run` REST endpoint, then an authenticated
    client can construct an HTTP PUT request to execute arbitrary code on the
    agent. This issue is made worse by the fact that puppet agents typically
    run as root.

CVE-2013-1654

    A bug in Puppet allows SSL connections to be downgraded to SSLv2, which is
    known to contain design flaw weaknesses This affects SSL connections
    between puppet agents and master, as well as connections that puppet agents
    make to third party servers that accept SSLv2 connections. Note that SSLv2
    is disabled since OpenSSL 1.0.

CVE-2013-1655

    An unauthenticated malicious client may send requests to the puppet master,
    and have the master load code in an unsafe manner. It only affects users
    whose puppet masters are running ruby 1.9.3 and above.

CVE-2013-2274

    An authenticated malicious client may execute arbitrary code on the
    puppet master in its default configuration. Given a valid certificate and
    private key, a client can construct an HTTP PUT request that is authorized
    to save the client's own report, but the request will actually cause the
    puppet master to execute arbitrary code.

CVE-2013-2275

    The default auth.conf allows an authenticated node to submit a report for
    any other node, which is a problem for compliance. It has been made more
    restrictive by default so that a node is only allowed to save its own
    report.

For the stable distribution (squeeze), these problems have been fixed in
version 2.6.2-5+squeeze7.

For the testing distribution (wheezy), these problems have been fixed in
version 2.7.18-3.

For the unstable distribution (sid), these problems have been fixed in
version 2.7.18-3.

We recommend that you upgrade your puppet packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: http://www.debian.org/security/

Mailing list: debian-security-announce@...ts.debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBCgAGBQJRP7CzAAoJEG3bU/KmdcClzGIIAI90dF51SNHLGAIImu6vXJd2
4PII5l3AeAyL8f7HQWqVgFYrockwsCazs/vgqPdwfDEAnon2C/I4FvpehJo5hd5y
dFH01a7KYEvgG1okfiuDk+Pe3AEQsJSbBSyhA/Yw4Uix4wk508TWjvUAUMjRnUn5
yO0dB3b3hj4xgESmKtlXbHpjeQaaVOh5emXLuaV5V9mxCCN0fedIqjKxWd4vN4E9
l7hin1DzuxwkwoKeCGDOjKcSShpHAvwspTsUFZMhcU33Mu2an5j0QgPBhiQthJ1r
5uNeOYyYq+DVD0wjO++Lo2KwUayQUOriL+6y1BUvheyc/o+408/jppJ1JLjIWyg=
=Z1A4
-----END PGP SIGNATURE-----