CVE-2013-1655: Puppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, when running Ruby 1.9.3 or later, allows remote attackers t

This month

HIGH 7.5DOWNGRADEDOWNGRADEDOWNGRADE

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

Puppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, when running Ruby 1.9.3 or later, allows remote attackers to execute arbitrary code via vectors related to "serialized attributes."

Why this priority

High severity
EPSS top 8%: very likely to be exploited

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	4.6% (top 8%)
CISA exploited list	No
Weakness	CWE-20
Published	2013-03-20
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: 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:51 UTCUpdated Record last modified

puppet puppet DOWNGRADE

Affected: 2.7.2 · 2.7.3 · 2.7.4 · 2.7.5 · 2.7.6 · 2.7.7 · 2.7.8 · 2.7.9

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.7.2

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 2.7.2 (Debian / Ubuntu)

apt-cache madison puppet sudo apt install puppet=<VERSION_BEFORE_2.7.2> 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.7.2> 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

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.1.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 3.1.0 (Debian / Ubuntu)

apt-cache madison puppet-enterprise sudo apt install puppet-enterprise=<VERSION_BEFORE_3.1.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_3.1.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.

puppetlabs puppet DOWNGRADE

Affected: 2.7.0 · 2.7.1 · 2.7.19 · 2.7.20 · 2.7.20 rc1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.7.0

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 2.7.0 (Debian / Ubuntu)

apt-cache madison puppet sudo apt install puppet=<VERSION_BEFORE_2.7.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.7.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-1655?

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

Is CVE-2013-1655 being exploited?

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

CVE-2013-1655 affects puppet, puppet enterprise, puppet. Severity is high (CVSS 7.5). Puppet 2.7.x before 2.7.21 and 3.1.x before 3.1.1, when running Ruby 1.9.3 or later, allows remote attackers to execute arbitrary code via vectors related to "serialized attributes."

How urgent is CVE-2013-1655?

Priority 49/100. High severity; EPSS top 8%: very likely to be exploited

Software pages

Ruby 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