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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
EUVD-2019-0007 | 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. |
![]() |
GHSA-p75j-wc34-527c | Exposure of Sensitive Information to an Unauthorized Actor in ansible |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2024-08-04T22:17:18.921Z
Reserved: 2019-03-27T00:00:00
Link: CVE-2019-10217

No data.

Status : Modified
Published: 2019-11-25T16:15:13.347
Modified: 2024-11-21T04:18:40.660
Link: CVE-2019-10217


No data.