CVE-2013-2275: The default configuration for puppet masters 0.25.0 and later in Puppet before 2.6.18, 2.7.x before 2.7.21, an

This month

MEDIUM 4.0WATCHLISTDOWNGRADEUPGRADEDOWNGRADE

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

The default configuration for puppet masters 0.25.0 and later in 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 nodes to submit reports for other nodes via unspecified vectors.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	4.0 (Medium)
EPSS exploit chance	2.9% (top 13%)
CISA exploited list	No
Published	2013-03-20
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: canonical · puppet · puppetlabs

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

Am I affected?

Timeline

2013-03-20 16:55 UTCPublished CVE record published
2026-06-16 23:53 UTCUpdated Record last modified

puppet puppet DOWNGRADE

Affected: 2.6.0 · 2.6.1 · 2.6.2 · 2.6.3 · 2.6.4 · 2.6.5 · 2.6.6 · 2.6.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.6.0

1. Check installed version

apt-cache policy puppet || rpm -q puppet || puppet --version

2. No fixed release: 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

2. No fixed release: 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 UPGRADE

Affected: <= 2.6.17 · 2.7.0 · 2.7.1 · 2.7.19 · 2.7.20 · 2.7.20 rc1 · <= 1.2.6

Fixed in: newer than 2.6.17

Safe to downgrade to: no unaffected older release

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.

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-2275?

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

Is CVE-2013-2275 being exploited?

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

CVE-2013-2275 affects puppet, puppet, puppet enterprise. Severity is medium (CVSS 4.0). The default configuration for puppet masters 0.25.0 and later in 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 nodes to submit repor

How urgent is CVE-2013-2275?

Priority 41/100. On your watchlist

Software pages

Ubuntu vulnerabilities

Related CVEs

CVE-2021-27026 MEDIUM 4.4 UPGRADE UPGRADE A flaw was divered in Puppet Enterprise and other Puppet products where sensitive plan parameters may be logge
CVE-2021-27025 MEDIUM 6.5 UPGRADE UPGRADE A flaw was discovered in Puppet Agent where the agent may silently ignore Augeas settings or may be vulnerable
CVE-2021-27022 MEDIUM 4.9 UPGRADE UPGRADE A flaw was discovered in bolt-server and ace where running a task with sensitive parameters results in those s
CVE-2021-27021 HIGH 8.8 UPGRADE UPGRADE A flaw was discovered in Puppet DB, this flaw results in an escalation of privileges which allows the user to
CVE-2020-7942 MEDIUM 6.5 UPGRADE UPGRADE Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in

References

← Back to latest CVEs