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.
CPE | Name | Operator | Version |
---|---|---|---|
ubuntu_linux | eq | 16.04 | |
ubuntu_linux | eq | 18.04 | |
ubuntu_linux | eq | 19.04 | |
debian_linux | eq | 9.0 | |
ansible_engine | eq | 2.0 | |
ansible_engine | gt | 2.5 | |
ansible_engine | le | 2.5.5 | |
ansible_engine | ge | 2.4 | |
ansible_engine | lt | 2.4.5 | |
cloudforms | eq | 4.6 |
access.redhat.com/errata/RHBA-2018:3788
access.redhat.com/errata/RHSA-2018:1948
access.redhat.com/errata/RHSA-2018:1949
access.redhat.com/errata/RHSA-2018:2022
access.redhat.com/errata/RHSA-2018:2079
access.redhat.com/errata/RHSA-2018:2184
access.redhat.com/errata/RHSA-2018:2585
access.redhat.com/errata/RHSA-2019:0054
bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10855
usn.ubuntu.com/4072-1/
www.debian.org/security/2019/dsa-4396