CVE-2013-4260
UnknownEPSS 0.33%
Last modified
CVE-2013-4260 is a vulnerability of currently unknown severity. 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/.. EPSS estimates a 0.33% chance of exploitation in the next 30 days.
Description
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/.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Redhat | Ansible | 1.2 |
| Redhat | Ansible | 1.2.1 |
| Redhat | Ansible | 1.2.2 |
References
- http://www.ansible.com/securityVendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=998227Issue Tracking, Patch
- https://exchange.xforce.ibmcloud.com/vulnerabilities/86898VDB Entry, Vendor Advisory
- http://www.ansible.com/securityVendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=998227Issue Tracking, Patch
- https://exchange.xforce.ibmcloud.com/vulnerabilities/86898VDB Entry, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-4260?
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/.
How severe is CVE-2013-4260?
Severity scoring for CVE-2013-4260 is pending analysis. The EPSS model estimates a 0.33% probability of exploitation in the next 30 days.
How do I fix CVE-2013-4260?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2013-4260?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
