Ansible Sensitive Files Are Locally Readable
The vault subsystem in Ansible before 1.5.5 does not set the umask before creation or modification of a vault file, which allows local users to obtain sensitive key information by reading a file.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-4658US | medium5.5 | — | ||
The vault subsystem in Ansible before 1.5.5 does not set the umask before creation or modification of a vault file, which allows local users to obtain sensitive key information by… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/ansible/ansiblePACKAGE
- https://github.com/ansible/ansible/blob/release1.5.5/CHANGELOG.mdWEB
- https://github.com/ansible/ansible/commit/a0e027fe362fbc209dbeff2f72d6e95f39885c69WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-200.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2014-4658ADVISORY
- https://web.archive.org/web/20210120133853/https://www.securityfocus.com/bid/68233WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan