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.
The product writes sensitive information to a log file.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2018:1949 | vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10855 | issue tracking vendor advisory |
https://access.redhat.com/errata/RHBA-2018:3788 | vendor advisory |
https://access.redhat.com/errata/RHSA-2018:1948 | vendor advisory |
https://access.redhat.com/errata/RHSA-2018:2184 | vendor advisory |
https://access.redhat.com/errata/RHSA-2018:2022 | vendor advisory |
https://access.redhat.com/errata/RHSA-2019:0054 | vendor advisory |
https://access.redhat.com/errata/RHSA-2018:2079 | vendor advisory |
https://access.redhat.com/errata/RHSA-2018:2585 | vendor advisory |
https://www.debian.org/security/2019/dsa-4396 | third party advisory vendor advisory |
https://usn.ubuntu.com/4072-1/ | third party advisory vendor advisory |