Description
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.
CVSS breakdown
CVSS 3.0
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
Affected products
- Unknown / ansibleAnsible 2.4.5 – Ansible 2.4.5
- Unknown / ansibleAnsible 2.5.5 – Ansible 2.5.5
References
- VENDOR_ADVISORYhttps://access.redhat.com/errata/RHSA-2018:1949
- MISChttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10855
- VENDOR_ADVISORYhttps://access.redhat.com/errata/RHBA-2018:3788
- VENDOR_ADVISORYhttps://access.redhat.com/errata/RHSA-2018:1948
- VENDOR_ADVISORYhttps://access.redhat.com/errata/RHSA-2018:2184
- VENDOR_ADVISORYhttps://access.redhat.com/errata/RHSA-2018:2022
- VENDOR_ADVISORYhttps://access.redhat.com/errata/RHSA-2019:0054
- VENDOR_ADVISORYhttps://access.redhat.com/errata/RHSA-2018:2079
- VENDOR_ADVISORYhttps://access.redhat.com/errata/RHSA-2018:2585
- VENDOR_ADVISORYhttps://www.debian.org/security/2019/dsa-4396
- VENDOR_ADVISORYhttps://usn.ubuntu.com/4072-1/