CVE-2013-2716: Medium severity puppet enterprise vulnerability

Published Apr 10, 2013
·
Updated

Puppet Labs Puppet Enterprise before 2.8.0 does not use a "randomized secret" in the CAS client config file (casclientconfig.yml) when upgrading from older 1.2.x or 2.0.x versions, which allows remote attackers to obtain console access via a crafted cookie.

Affected Software

9 affected components
Puppet Puppet Enterprise<=2.7.2
Puppet Puppet Enterprise=2.0.0
Puppet Puppet Enterprise=2.5.1
Puppet Puppet Enterprise=2.5.2
Puppetlabs Puppet=1.0.0
Puppetlabs Puppet=1.1.0
Puppetlabs Puppet=1.2.0
Puppetlabs Puppet=2.5.0
Puppetlabs Puppet=2.6.0

Event History

Apr 10, 2013
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03: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-2716?

CVE-2013-2716 is considered a high severity vulnerability due to its potential to allow unauthorized console access.

2

How do I fix CVE-2013-2716?

To fix CVE-2013-2716, upgrade to Puppet Enterprise version 2.8.0 or later.

3

What causes CVE-2013-2716?

CVE-2013-2716 is caused by the lack of a randomized secret in the CAS client configuration when upgrading from older versions.

4

Which versions of Puppet Enterprise are affected by CVE-2013-2716?

Puppet Enterprise versions prior to 2.8.0, including 1.2.x, 2.0.x, up to 2.7.2, are affected by CVE-2013-2716.

5

Can CVE-2013-2716 be exploited remotely?

Yes, CVE-2013-2716 can be exploited remotely by using a crafted cookie to gain console access.

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