CVE-2019-10217 — Sensitive Information Exposure in Redhat Ansible

CWE-200 — Sensitive Information Exposure8 documents7 sources
Severity
6.5MEDIUMNVD
EPSS
0.4%
top 37.68%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
2
Redhat AnsibleRED HAT Ansible
Timeline
PublishedNov 25
Latest updateOct 12

Description

A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitability: 2.8 | Impact: 3.6

Affected Packages4 packages

▶NVDredhat/ansible2.8.0 — 2.8.4
▶PyPIredhat/ansible2.8.0a1 — 2.8.4
▶Debianredhat/ansible< 2.8.6+dfsg-1+3
▶CVEListV5red_hat/ansibleansible 2.8.0 before 2.8.4

🔴Vulnerability Details

4
GHSA
Exposure of Sensitive Information to an Unauthorized Actor in ansible↗2021-10-12
▶
OSV
Exposure of Sensitive Information to an Unauthorized Actor in ansible↗2021-10-12
▶
OSV
CVE-2019-10217: A flaw was found in ansible 2↗2019-11-25
▶
CVEList
CVE-2019-10217: A flaw was found in ansible 2↗2019-11-25
▶

📋Vendor Advisories

2
Red Hat
Ansible: gcp modules do not flag sensitive data fields properly↗2019-07-26
▶
Debian
CVE-2019-10217: ansible - A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data s...↗2019
▶

💬Community

1
Bugzilla
CVE-2019-10217 Ansible: gcp modules do not flag sensitive data fields properly↗2019-07-26
▶
CVE-2019-10217 — Sensitive Information Exposure | cvebase