First published: Fri Jul 26 2019(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Redhat Ansible | >=2.8.0<2.8.4 | |
redhat/ansible-engine | <2.8.4 | 2.8.4 |
pip/ansible | >=2.8.0a1<2.8.4 | 2.8.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2019-10217.
The severity of CVE-2019-10217 is medium.
The affected software version is ansible 2.8.0.
To fix CVE-2019-10217, upgrade ansible to version 2.8.4 or later.
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).