DescriptionAnsible 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.
Overall state of this security issue: Resolved
This issue is currently rated as having moderate severity.
|National Vulnerability Database|
|National Vulnerability Database||SUSE|
- SUSE-SU-2018:4130-1, published Fri Dec 14 13:11:19 MST 2018
- openSUSE-SU-2019:0238-1, published Sat, 23 Feb 2019 15:08:47 +0100 (CET)
List of released packages
|Product(s)||Fixed package version(s)||References|
|HPE Helion Openstack 8|| ||Patchnames:
|SUSE OpenStack Cloud 8|| ||Patchnames:
|SUSE OpenStack Cloud Crowbar 8|| ||Patchnames:
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification.
|HPE Helion OpenStack 8||ansible||Affected|
|SUSE Openstack Cloud 7||ansible||Not affected|
|SUSE Openstack Cloud 8||ansible||Released|