An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.
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 |
|---|---|---|---|
| Ansible_engine | Redhat | * | 2.9.12 (excluding) |
| Ansible | Ubuntu | bionic | * |
| Ansible | Ubuntu | eoan | * |
| Ansible | Ubuntu | groovy | * |
| Ansible | Ubuntu | hirsute | * |
| Ansible | Ubuntu | impish | * |
| Ansible | Ubuntu | kinetic | * |
| Ansible | Ubuntu | lunar | * |
| Ansible | Ubuntu | mantic | * |
| Ansible | Ubuntu | trusty | * |
| Ansible | Ubuntu | trusty/esm | * |
| Ansible | Ubuntu | xenial | * |
| Red Hat Ansible Engine 2.8 for RHEL 7 | RedHat | ansible-0:2.8.15-1.el7ae | * |
| Red Hat Ansible Engine 2.8 for RHEL 8 | RedHat | ansible-0:2.8.15-1.el8ae | * |
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: