CVE-2019-10217

Ansible: gcp modules do not flag sensitive data fields properly

Published Nov 25, 2019 CVSS 3.1 · 6.5 Medium EPSS 1.9% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD 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.
Github GHSA Github GHSA GHSA-p75j-wc34-527c Exposure of Sensitive Information to an Unauthorized Actor in ansible
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Aug 4, 2024, 10:17 PM
Reserved
Mar 27, 2019, 12:00 AM
Status
Modified
Published
Nov 25, 2019, 4:15 PM
Modified
Jun 17, 2026, 2:10 AM
Severity
Moderate
Public date
Jul 26, 2019, 12:00 AM