CVE-2019-10217: Infoleak
A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by nolog feature. Some of these fields in GCP modules are not set properly. serviceaccountcontents() which is common class for all gcp modules is not setting nolog to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/ansible-engineto a version that resolves this vulnerability.Fixed in 2.8.4 - Upgrade
Upgrade
pip/ansibleto a version that resolves this vulnerability.Fixed in 2.8.4 - Upgrade
Upgrade
alpine/ansibleto a version that resolves this vulnerability.Fixed in 2.8.4-r0 - Upgrade
Upgrade
alpine/ansible-baseto a version that resolves this vulnerability.Fixed in 2.8.4-r0
Event History
Frequently Asked Questions
What is the vulnerability ID of this flaw?
The vulnerability ID is CVE-2019-10217.
What is the severity of CVE-2019-10217?
The severity of CVE-2019-10217 is medium.
Which software version is affected by CVE-2019-10217?
The affected software version is ansible 2.8.0.
How can I fix CVE-2019-10217?
To fix CVE-2019-10217, upgrade ansible to version 2.8.4 or later.
Are there any references available for CVE-2019-10217?
Yes, the references for CVE-2019-10217 are available at the following links: [reference 1](https://github.com/ansible/ansible/issues/56269), [reference 2](https://github.com/ansible/ansible/pull/59427), [reference 3](https://github.com/ansible/ansible-stage/pull/7).