CVE-2012-3866: lib/puppet/defaults.rb in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permission

Q: How do I fix CVE-2012-3866?

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

Q: Is CVE-2012-3866 being exploited?

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

Q: What does CVE-2012-3866 affect?

CVE-2012-3866 affects puppet, puppet, puppet enterprise. Severity is low (CVSS 2.1). lib/puppet/defaults.rb in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for last_run_report.yaml, which allows local users to obtain sensitive configuration information by leveraging access to the pup

Q: How urgent is CVE-2012-3866?

Priority 23/100. Public exploit reference

Routine

LOW 2.1DOWNGRADEUPGRADEUPGRADE

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

lib/puppet/defaults.rb in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for last_run_report.yaml, which allows local users to obtain sensitive configuration information by leveraging access to the puppet master server to read this file.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	2.1 (Low)
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-264
Published	2012-08-06
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

2012-08-06 16:55 UTCPublished CVE record published
2026-06-16 23:44 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.8 · 2.7.9 · 2.7.10

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.

puppetlabs puppet UPGRADE

Affected: <= 2.7.17 · 2.7.0 · 2.7.1

Fixed in: newer than 2.7.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.7.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 UPGRADE

Affected: <= 2.5.1

Fixed in: newer than 2.5.1

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.5.1 (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.

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-2012-3866?

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

Is CVE-2012-3866 being exploited?

CVE-2012-3866 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-2012-3866 affect?

CVE-2012-3866 affects puppet, puppet, puppet enterprise. Severity is low (CVSS 2.1). lib/puppet/defaults.rb in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for last_run_report.yaml, which allows local users to obtain sensitive configuration information by leveraging access to the pup

How urgent is CVE-2012-3866?

Priority 23/100. Public exploit reference

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