Ansible: gcp modules do not flag sensitive data fields properly
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Ansible | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Ansible Engine 2.8 for RHEL 7 | |||
| ansible-0:2.8.4-1.el7ae | cpe:/a:redhat:ansible_engine:2.8::el7 | RHSA-2019:2542 | 2019-08-21T00:00:00Z |
| Red Hat Ansible Engine 2.8 for RHEL 8 | |||
| ansible-0:2.8.4-1.el8ae | cpe:/a:redhat:ansible_engine:2.8::el8 | RHSA-2019:2542 | 2019-08-21T00:00:00Z |
| Red Hat Ansible Engine 2 for RHEL 7 | |||
| ansible-0:2.8.4-1.el7ae | cpe:/a:redhat:ansible_engine:2::el7 | RHSA-2019:2543 | 2019-08-21T00:00:00Z |
| Red Hat Ansible Engine 2 for RHEL 8 | |||
| ansible-0:2.8.4-1.el8ae | cpe:/a:redhat:ansible_engine:2::el8 | RHSA-2019:2543 | 2019-08-21T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
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 |
GHSA-p75j-wc34-527c | Exposure of Sensitive Information to an Unauthorized Actor in ansible |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 1.9% (1.853% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.