Bug 919774 (CVE-2013-1653) - CVE-2013-1653 Puppet: kick connection HTTP PUT request arbitrary code execution
Summary: CVE-2013-1653 Puppet: kick connection HTTP PUT request arbitrary code execution
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-1653
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 920845
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-10 01:53 UTC by Kurt Seifried
Modified: 2019-09-29 13:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-24 15:36:27 UTC
Embargoed:


Attachments (Terms of Use)

Description Kurt Seifried 2013-03-10 01:53:19 UTC
Moses Mendoza (moses) reports:

CVE-2013-1653 - Remote code execution
* Affected versions: 2.7.0 and greater
* Patched versions: 2.7.x, 3.1.x

A bug in Puppet allows authenticated clients to 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.


External References:
https://puppetlabs.com/security/cve/cve-2013-1653/

Comment 1 Vincent Danen 2013-03-12 21:40:45 UTC
Created puppet tracking bugs for this issue

Affects: fedora-all [bug 920845]

Comment 2 Kurt Seifried 2013-03-15 04:59:07 UTC
For the puppet roll-up patches please see Bz 919783 for the patch files.

Comment 3 Fedora Update System 2013-08-02 03:24:13 UTC
puppet-3.1.1-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.