Skip to content
Fencer Intel
medium 6.2

CVE-2013-4260 json

Ansible Arbitrary File Overwrite Vulnerability

published 13y ago modified 4mo ago also GHSA-pcqv-c46v-2p4v , PYSEC-2013-2 , EUVD-2013-0002

cvss
6.2
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

lib/ansible/playbook/__init__.py in Ansible 1.2.x before 1.2.3, when playbook does not run due to an error, allows local users to overwrite arbitrary files via a symlink attack on a retry file with a predictable name in /var/tmp/ansible/.

Patch / fix

  • pypi ansible 1.2.3

Is CVE-2013-4260 in your dependencies? 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-4260 updated cvss 3.6

ansible: predictible filename used for failed result in world writable directory

  • Red Hat All currently supported Red Hat products
    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.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:N/I:P/A:P
GitHub 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi ansible
>=1.2, <1.2.3
>=1.2.0, <1.2.3
1.2.3

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-281 Improper Preservation of Permissions

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.