Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2013-2716: Puppet Labs Puppet Enterprise before 2.8.0 does not use a "randomized secret" in the CAS client config file (c

35
Routine
MEDIUM 5.0UPGRADEDOWNGRADE

CVE-2013-2716 is a medium-severity flaw (CVSS 5.0) affecting puppet enterprise, puppet. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Puppet Labs Puppet Enterprise before 2.8.0 does not use a "randomized secret" in the CAS client config file (cas_client_config.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.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score5.0 (Medium)
EPSS exploit chance1.3% (top 29%)
CISA exploited listNo
WeaknessCWE-310
Published2013-04-10
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: puppet · puppetlabs

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

puppet puppet enterprise UPGRADE
Affected: <= 2.7.2 · 2.0.0 · 2.5.1 · 2.5.2
Fixed in: newer than 2.7.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy puppet-enterprise || rpm -q puppet-enterprise || puppet-enterprise --version
2. UPGRADE to newer than 2.7.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade puppet-enterprise
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade puppet-enterprise
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
puppetlabs puppet DOWNGRADE
Affected: 1.0.0 · 1.1.0 · 1.2.0 · 2.5.0 · 2.6.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy puppet || rpm -q puppet || puppet --version
2. No fixed release: DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison puppet sudo apt install puppet=<VERSION_BEFORE_1.0.0> sudo apt-mark hold puppet
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list puppet sudo dnf downgrade puppet-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add puppet
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-2716?

puppet enterprise: upgrade to newer than 2.7.2; puppet: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2013-2716 being exploited?

CVE-2013-2716 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-2716 affect?

CVE-2013-2716 affects puppet enterprise, puppet. Severity is medium (CVSS 5.0). Puppet Labs Puppet Enterprise before 2.8.0 does not use a "randomized secret" in the CAS client config file (cas_client_config.yml) when upgrading from older 1.2.x or 2.0.x versions, which allows remote attackers to obtain console access vi

How urgent is CVE-2013-2716?

Priority 35/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.