CVE-2013-1652: Medium severity puppet vulnerability

Published Mar 20, 2013
·
Updated

Puppet before 2.6.18, 2.7.x before 2.7.21, and 3.1.x before 3.1.1, and Puppet Enterprise before 1.2.7 and 2.7.x before 2.7.2 allows remote authenticated users with a valid certificate and private key to read arbitrary catalogs or poison the master's cache via unspecified vectors.

Affected Software

29 affected components
Puppetlabs Puppet<=2.6.17
Puppet Puppet=2.7.2
Puppet Puppet=2.7.3
Puppet Puppet=2.7.4
Puppet Puppet=2.7.5
Puppet Puppet=2.7.6
Puppet Puppet=2.7.7
Puppet Puppet=2.7.8
Puppet Puppet=2.7.9
Puppet Puppet=2.7.10
Puppet Puppet=2.7.11
Puppet Puppet=2.7.12
Puppet Puppet=2.7.13
Puppet Puppet=2.7.14
Puppet Puppet=2.7.16
Puppet Puppet=2.7.17
Puppet Puppet=2.7.18
Puppetlabs Puppet=2.7.0
Puppetlabs Puppet=2.7.1
Puppetlabs Puppet=2.7.19
Puppetlabs Puppet=2.7.20
Puppetlabs Puppet=2.7.20-rc1
Puppet Puppet Enterprise=3.1.0
Puppetlabs Puppet<=1.2.6
Puppet Puppet Enterprise=2.7.0
Puppet Puppet Enterprise=2.7.1
Canonical Ubuntu Linux=11.10
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=12.10

Event History

Mar 20, 2013
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-1652?

CVE-2013-1652 is considered a critical vulnerability due to its potential to allow remote authenticated users to read arbitrary catalogs or poison the master's cache.

2

How do I fix CVE-2013-1652?

To fix CVE-2013-1652, upgrade to Puppet 2.6.18 or higher, Puppet 2.7.21 or higher, or Puppet Enterprise 1.2.7 or higher.

3

Who is affected by CVE-2013-1652?

CVE-2013-1652 affects users of Puppet versions prior to 2.6.18, 2.7.x prior to 2.7.21, and 3.1.x prior to 3.1.1.

4

What type of access does CVE-2013-1652 allow?

CVE-2013-1652 allows remote authenticated users with a valid certificate and private key to configure Puppet master behaviors.

5

Is there a workaround for CVE-2013-1652?

There are no known workarounds for CVE-2013-1652; the recommended course of action is to apply the necessary updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203