CVE-2018-10855: Ansible exposes sensitive data in log files and on the terminal
(updated )
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
- 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
- github.com/advisories/GHSA-jwcc-j78w-j73w
- github.com/ansible/ansible
- github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2018-42.yaml
- nvd.nist.gov/vuln/detail/CVE-2018-10855
- usn.ubuntu.com/4072-1
- www.debian.org/security/2019/dsa-4396
Code Behaviors & Features
Detect and mitigate CVE-2018-10855 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →