CVE-2019-10217: Exposure of Sensitive Information to an Unauthorized Actor in ansible
(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.
References
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10217
- github.com/advisories/GHSA-p75j-wc34-527c
- github.com/ansible/ansible
- github.com/ansible/ansible/commit/c1ee1f142db1e669b710a65147ea32be47a91519
- github.com/ansible/ansible/issues/56269
- github.com/ansible/ansible/pull/59427
- github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2019-3.yaml
- nvd.nist.gov/vuln/detail/CVE-2019-10217
Code Behaviors & Features
Detect and mitigate CVE-2019-10217 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →