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.
2018-07-03T01:29:00.580
2024-11-21T03:42:08.980
Modified
CVSSv3.1: 5.9 (MEDIUM)
AV:N/AC:M/Au:N/C:P/I:N/A:N
8.6
2.9
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | redhat | ansible_engine | < 2.4.5 | Yes |
Application | redhat | ansible_engine | ≤ 2.5.5 | Yes |
Application | redhat | ansible_engine | 2.0 | Yes |
Application | redhat | cloudforms | 4.6 | Yes |
Application | redhat | openstack | 13 | Yes |
Application | redhat | virtualization | 4.0 | Yes |
Operating System | debian | debian_linux | 9.0 | Yes |
Application | redhat | openstack | 10 | Yes |
Application | redhat | openstack | 12 | Yes |
Operating System | canonical | ubuntu_linux | 16.04 | Yes |
Operating System | canonical | ubuntu_linux | 18.04 | Yes |
Operating System | canonical | ubuntu_linux | 19.04 | Yes |