Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2013-1653: 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.

53
This month
HIGH 7.1WATCHLISTUPGRADEDOWNGRADEDOWNGRADE

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

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, when listening for incoming connections is enabled and allowing access to the "run" REST endpoint is allowed, allows remote authenticated users to execute arbitrary code via a crafted HTTP request.

Why this priority

  • High severity
  • EPSS top 7%: very likely to be exploited
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.1 (High)
EPSS exploit chance5.4% (top 7%)
CISA exploited listNo
Published2013-03-20
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: canonical · 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 UPGRADE
Affected: >= 2.6.0 and <= 2.6.17 · 2.7.2 · 2.7.3 · 2.7.4 · 2.7.5 · 2.7.6 · 2.7.7 · 2.7.8
Fixed in: newer than 2.6.17
Safe to downgrade to: a release before 2.6.0
1. Check installed version
apt-cache policy puppet || rpm -q puppet || puppet --version
2. UPGRADE to newer than 2.6.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade puppet
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade puppet
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.6.0 (Debian / Ubuntu)
apt-cache madison puppet sudo apt install puppet=<VERSION_BEFORE_2.6.0> sudo apt-mark hold puppet
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list puppet sudo dnf downgrade puppet-<VERSION_BEFORE_2.6.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.
puppetlabs puppet DOWNGRADE
Affected: 2.7.0 · 2.7.1 · 2.7.19 · 2.7.20 · 2.7.20 rc1 · 1.0 · 1.1 · 1.2.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.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 (Debian / Ubuntu)
apt-cache madison puppet sudo apt install puppet=<VERSION_BEFORE_1.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> 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.
puppet puppet enterprise DOWNGRADE
Affected: 3.1.0 · 2.7.0 · 2.7.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.7.0
1. Check installed version
apt-cache policy puppet-enterprise || rpm -q puppet-enterprise || puppet-enterprise --version
2. No fixed release: DOWNGRADE to a release before 2.7.0 (Debian / Ubuntu)
apt-cache madison puppet-enterprise sudo apt install puppet-enterprise=<VERSION_BEFORE_2.7.0> sudo apt-mark hold puppet-enterprise
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list puppet-enterprise sudo dnf downgrade puppet-enterprise-<VERSION_BEFORE_2.7.0> sudo dnf versionlock add puppet-enterprise
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.
canonical ubuntu linux MITIGATE
Affected: 11.10 · 12.04 · 12.10
Fixed in: no fixed release known
Safe to downgrade to: a release before 11.10
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
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-1653?

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

Is CVE-2013-1653 being exploited?

CVE-2013-1653 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-1653 affect?

CVE-2013-1653 affects puppet, puppet, puppet enterprise. Severity is high (CVSS 7.1). 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, when listening for incoming connections is enabled and allowing access to the "run" REST endpoint is allowed, allo

How urgent is CVE-2013-1653?

Priority 53/100. High severity; EPSS top 7%: very likely to be exploited; On your watchlist

Software pages

Ubuntu vulnerabilities

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.