CVE-2019-14864PYSEC-2020-160GHSA-3M93-M4Q6-MC6V
Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it
- 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.7.15, 2.8.7, 2.9.1
- 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
Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.
Timeline
- CVE published
- Record last updated
Affected versions
- Red Hat Ansible
Ansible versions 2.9.x before 2.9.1, Ansible versions 2.8.x before 2.8.7, Ansible versions 2.7.x before 2.7.15
- ansiblePyPI
From 2.7.0 · fixed in 2.7.15; From 2.8.0 · fixed in 2.8.7; From 2.9.0 · fixed in 2.9.1
- ansiblePyPI
From 2.7.0a1 · fixed in 2.7.15
- ansiblePyPI
From 2.8.0a1 · fixed in 2.8.7
- ansiblePyPI
From 2.9.0a1 · fixed in 2.9.1