MediumGHSA-5g4v-2pc6-4hh4CVE-2014-4658PYSEC-2020-200
Ansible Sensitive Files Are Locally Readable
Published 17 May 2022 · Updated 17 Feb 2025
Is your project on an affected ansible?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
ansiblePyPI
- Affected
- <1.5.5
- Fixed in
- 1.5.5
Update to the fixed version for your release line, for example:
pip install 'ansible>=1.5.5'Details
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.
Is GHSA-5g4v-2pc6-4hh4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected ansible, and gives you the command that fixes it.
More advisories for ansible
- MediumCVE-2025-14010Ansible Community General Collection is vulnerable to exposure of sensitive information · 4 Dec 2025
- MediumCVE-2020-25635Ansible does not collect garbage after playbook run · 31 Oct 2025
- MediumCVE-2023-5115Ansible symlink attack vulnerability · 28 Dec 2023
- HighCVE-2022-3697Ansible leaks password to logs · 28 Oct 2022
- HighCVE-2021-20228Ansible Exposes Sensitive Information · 25 May 2022
- CriticalCVE-2014-4678Ansible Code Injection Vulnerability · 24 May 2022
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2014-4658
- Linkgithub.com/ansible/ansible/commit/a0e027fe362fbc209dbeff2f72d6e95f39885c69
- Packagegithub.com/ansible/ansible
- Linkgithub.com/ansible/ansible/blob/release1.5.5/CHANGELOG.md
- Linkgithub.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-200.yaml
- Linkweb.archive.org/web/20210120133853/https://www.securityfocus.com/bid/68233
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.