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.
References
Link | Resource |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10855 | Issue Tracking Vendor Advisory |
https://access.redhat.com/errata/RHSA-2018:2079 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2018:2022 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2018:1949 | 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:2585 | Vendor Advisory |
https://access.redhat.com/errata/RHBA-2018:3788 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2019:0054 | Vendor Advisory |
https://www.debian.org/security/2019/dsa-4396 | Third Party Advisory |
https://usn.ubuntu.com/4072-1/ | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Information
Published : 2018-07-02 18:29
Updated : 2021-08-04 10:14
NVD link : CVE-2018-10855
Mitre link : CVE-2018-10855
JSON object : View
CWE
CWE-532
Insertion of Sensitive Information into Log File
Products Affected
redhat
- ansible_engine
- openstack
- virtualization
- cloudforms
canonical
- ubuntu_linux
debian
- debian_linux