CVE-2014-4658 json
Ansible Sensitive Files Are Locally Readable
published 2020-02-20 6 y ago modified 2026-06-17 4 mo ago also GHSA-5g4v-2pc6-4hh4 , PYSEC-2020-200 , EUVD-2020-0012
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi ansible 1.5.5
- redhat ansible 1.5.5
- ansible Debian 14, Debian 13, Debian 12 1.5.5+dfsg-1
debian advisories DEBIAN-CVE-2014-4658
- ansible Ubuntu Pro 14.04 LTS 1.5.4+dfsg-1ubuntu0.1~esm2
ubuntu advisories UBUNTU-CVE-2014-4658
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-4658 updated cvss 5.5
ansible: incorrect umask mode before creating/editing vault subsystem allows allows exposure of sensitive key information
-
Red Hat CloudForms Management Engine 5 ansible Red Hat Ansible Engine 2 ansible, ansible-test Red Hat Ansible Tower 3 ansible Red Hat Ceph Storage 2 ansible Red Hat Ceph Storage 3 ansible Red Hat OpenStack Platform 10 (Newton) ansiblenot affected: vulnerable code not present
+2 more productsfewer
Red Hat OpenStack Platform 13 (Queens) ansible Red Hat Storage 3 ansible
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | ansible | <1.5.5 |
1.5.5 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/ansible/ansible/commit/a0e027fe362fbc209dbeff2f72d6e95f39885c69
web
-
github.com
/ansible/ansible/blob/release1.5.5/CHANGELOG.md
web, release-notes
-
securityfocus.com
/bid/68233
vdb-entry, third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2014-4658
advisory
-
github.com
/ansible/ansible
package
-
github.com
/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-200.yaml
web
-
web.archive.org
/web/20210120133853/https://www.securityfocus.com/bid/68233
web
-
github.com
/advisories/GHSA-5g4v-2pc6-4hh4
advisory
Sources
- CVE List CVE-2014-4658
- GitHub Advisory GHSA-5g4v-2pc6-4hh4
- NVD CVE-2014-4658
- OSV PYSEC-2020-200
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.