cve.bz

CVE-2013-4969 Link Following

no score yetEPSS 0.4%

No CVSS score yet. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2013-4969 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2013-4969?via=ask-ai-copy and https://cve.bz/cve/CVE-2013-4969?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2013-4969 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
puppetlabs:puppetfrom 3.0.0 through 3.3.2
puppetlabs:puppetfrom 3.4.0 before 3.4.1
puppet:puppet_enterprisefrom 2.0.0 before 2.8.4
puppet:puppet_enterprisefrom 3.1 before 3.1.1
debian:debian_linux6.0
debian:debian_linux7.0
debian:debian_linux8.0
canonical:ubuntu_linux12.04
canonical:ubuntu_linux12.10
canonical:ubuntu_linux13.04
canonical:ubuntu_linux13.10

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian6.0puppet2.6.2-5+squeeze9DSA-2831-1
Debian7puppet2.7.23-1~deb7u2DSA-2831-1
Debian11puppet3.4.1-1DEBIAN-CVE-2013-4969
Azure Linux3puppetno fix listedAZL-45426

From the distributions' data via OSV.dev: the Debian Security Tracker; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat Product Security has rated this issue as having Low security impact in Subscription Asset Manager 1. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Red Hat Product Security has rated this issue as having Low security impact in Red Hat OpenStack Platform 4.0. This issue is not currently planned to be addressed in future updates.

ProductPackageStateAdvisory
CloudForms Management Engine 5puppetNot affected
Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse)puppetNot affected
Red Hat Enterprise MRG 1puppetWill not fix
Red Hat OpenStack Platform 3puppetWill not fix
Red Hat OpenStack Platform 3ruby193-puppetWill not fix
Red Hat OpenStack Platform 4puppetAffected
Red Hat Satellite 6ruby193-puppetAffected
Red Hat Subscription Asset ManagerpuppetWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2013-4969.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON