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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Link | Tags |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10217 | issue tracking third party advisory |
https://github.com/ansible/ansible/issues/56269 | third party advisory exploit |
https://github.com/ansible/ansible/pull/59427 | third party advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.html | vendor advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.html | vendor advisory |