CVE-2018-10855GHSA-JWCC-J78W-J73WPYSEC-2018-42
Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks.
- 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.5.5, 2.4.5.0
- 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 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.
Timeline
- CVE published
- Record last updated
Affected versions
- [UNKNOWN] ansible
Ansible 2.4.5, Ansible 2.5.5
- ansiblePyPI
From 2.5.0a1 · fixed in 2.5.5
- ansiblePyPI
From 2.4.0.0 · fixed in 2.4.5.0
- ansiblePyPI
From 2.5 · fixed in 2.5.5; From 2.4 · fixed in 2.4.5.0