Exposure of Sensitive Information to an Unauthorized Actor in ansible
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-10217US | medium6.5 | — | ||
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. se… | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.htmlWEB
- http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.htmlWEB
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10217WEB
- https://github.com/advisories/GHSA-p75j-wc34-527cADVISORY
- https://github.com/ansible/ansiblePACKAGE
- https://github.com/ansible/ansible/commit/c1ee1f142db1e669b710a65147ea32be47a91519WEB
- https://github.com/ansible/ansible/issues/56269WEB
- https://github.com/ansible/ansible/pull/59427WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan