CVE-2019-10217
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 2.8.6+dfsg-1 |
| sid | Fixed | 2.8.6+dfsg-1 |
| forky | Fixed | 2.8.6+dfsg-1 |
| bullseye | Fixed | 2.8.6+dfsg-1 |
| bookworm | Fixed | 2.8.6+dfsg-1 |
References
- https://security-tracker.debian.org/tracker/CVE-2019-10217
- https://nvd.nist.gov/vuln/detail/CVE-2019-10217
- https://github.com/ansible/ansible/issues/56269
- https://github.com/ansible/ansible/pull/59427
- https://github.com/ansible/ansible/commit/c1ee1f142db1e669b710a65147ea32be47a91519
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10217
- https://github.com/advisories/GHSA-p75j-wc34-527c
- https://github.com/ansible/ansible
- https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2019-3.yaml
- http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.html
- http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.