Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2013-4969: Puppet before 3.3.3 and 3.4 before 3.4.1 and Puppet Enterprise (PE) before 2.8.4 and 3.1 before 3.1.1 allows l

22
Routine
LOW 2.1WATCHLISTUPGRADEUPGRADEMITIGATE

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

Puppet before 3.3.3 and 3.4 before 3.4.1 and Puppet Enterprise (PE) before 2.8.4 and 3.1 before 3.1.1 allows local users to overwrite arbitrary files via a symlink attack on unspecified files.

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score2.1 (Low)
EPSS exploit chance0.4% (top 63%)
CISA exploited listNo
WeaknessCWE-59
Published2014-01-07
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: canonical · debian · 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

puppetlabs puppet UPGRADE
Affected: >= 3.0.0 and <= 3.3.2 · >= 3.4.0 and < 3.4.1
Fixed in: 3.4.1
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy puppet || rpm -q puppet || puppet --version
2. UPGRADE to 3.4.1 (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 3.0.0 (Debian / Ubuntu)
apt-cache madison puppet sudo apt install puppet=<VERSION_BEFORE_3.0.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_3.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.
puppet puppet enterprise UPGRADE
Affected: >= 2.0.0 and < 2.8.4 · >= 3.1 and < 3.1.1
Fixed in: 2.8.4, 3.1.1
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy puppet-enterprise || rpm -q puppet-enterprise || puppet-enterprise --version
2. UPGRADE to 2.8.4 (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.
3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison puppet-enterprise sudo apt install puppet-enterprise=<VERSION_BEFORE_2.0.0> sudo apt-mark hold puppet-enterprise
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list puppet-enterprise sudo dnf downgrade puppet-enterprise-<VERSION_BEFORE_2.0.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.
debian debian linux MITIGATE
Affected: 6.0 · 7.0 · 8.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0
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.
canonical ubuntu linux MITIGATE
Affected: 12.04 · 12.10 · 13.04 · 13.10
Fixed in: no fixed release known
Safe to downgrade to: a release before 12.04
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-4969?

puppet: upgrade to 3.4.1; puppet enterprise: upgrade to 2.8.4, 3.1.1; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2013-4969 being exploited?

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

CVE-2013-4969 affects puppet, puppet enterprise, debian linux. Severity is low (CVSS 2.1). Puppet before 3.3.3 and 3.4 before 3.4.1 and Puppet Enterprise (PE) before 2.8.4 and 3.1 before 3.1.1 allows local users to overwrite arbitrary files via a symlink attack on unspecified files.

How urgent is CVE-2013-4969?

Priority 22/100. On your watchlist

Software pages

Ubuntu vulnerabilities · Debian 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.