CVE-2019-10217PYSEC-2019-3GHSA-P75J-WC34-527C
A flaw was found in ansible 2.8.0 before 2.8.4.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.8.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Red Hat Ansible
ansible 2.8.0 before 2.8.4
- ansiblePyPI
From 2.8.0 · fixed in 2.8.4
- ansiblePyPI
From 2.8.0a1 · fixed in 2.8.4