Ansible exposes sensitive data in log files and on the terminal
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-10855US | medium5.9 | — | ||
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 tas… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHBA-2018:3788WEB
- https://access.redhat.com/errata/RHSA-2018:1948WEB
- https://access.redhat.com/errata/RHSA-2018:1949WEB
- https://access.redhat.com/errata/RHSA-2018:2022WEB
- https://access.redhat.com/errata/RHSA-2018:2079WEB
- https://access.redhat.com/errata/RHSA-2018:2184WEB
- https://access.redhat.com/errata/RHSA-2018:2585WEB
- https://access.redhat.com/errata/RHSA-2019:0054WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan