Exposure of Sensitive Information to an Unauthorized Actor in ansible
Moderate severity
GitHub Reviewed
Published
Oct 12, 2021
to the GitHub Advisory Database
•
Updated Sep 4, 2024
Description
Published by the National Vulnerability Database
Nov 25, 2019
Reviewed
Oct 8, 2021
Published to the GitHub Advisory Database
Oct 12, 2021
Last updated
Sep 4, 2024
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