Key disclosure via inherited umask on vault files
Published Feb 20, 2020 · Updated Aug 6, 2024
Information disclosure in Ansible Vault before 1.5.5 allows local users to read sensitive key information from vault files. The create_file and edit_file paths in lib/ansible/utils/vault.py create plaintext editor or temporary files before enforcing a restrictive umask. Exploitation requires local account access and a permissive process umask, exposing vault plaintext while a file is created or edited.
Summary
What happened
Information disclosure in Ansible Vault before 1.5.5 allows local users to read sensitive key information from vault files. The create_file and edit_file paths in lib/ansible/utils/vault.py create plaintext editor or temporary files before enforcing a restrictive umask. Exploitation requires local account access and a permissive process umask, exposing vault plaintext while a file is created or edited.
The record
- CVE
- CVE-2014-4658
- Published
- Feb 20, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo