Skip to content
Fencer Intel
low 2.1

CVE-2013-4969 json

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 arbit…

published 12y ago modified 4mo ago also EUVD-2013-4813

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

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.

Patch / fix

  • puppetlabs puppet 3.4.1
  • puppet puppet_enterprise 2.8.4, 3.1.1
  • puppet Debian 11 3.4.1-1

debian advisories DEBIAN-CVE-2013-4969

Is CVE-2013-4969 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-4969 updated cvss 2.1

Puppet: Unsafe use of Temp files in File type

  • Red Hat Enterprise MRG 1 puppet Red Hat OpenStack Platform 3 puppet, ruby193-puppet
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 4 puppet Red Hat Satellite 6 ruby193-puppet
    affected: no fix available
  • Red Hat Subscription Asset Manager puppet
    affected: no fix planned “Will not fix”
  • Red Hat CloudForms Management Engine 5 puppet Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) puppet
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.