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.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Virtualization | Redhat | 4.0 | 4.0 |
Cloudforms | Redhat | 4.6 | 4.6 |
Ansible_engine | Redhat | 2.0 | 2.0 |
Ansible_engine | Redhat | * | 2.5.5 |
Ansible_engine | Redhat | 2.4 | * |
Openstack | Redhat | 13 | 13 |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: