An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG configuration in some scenarios. Information is still included in the output in certain tasks, such as loop items. Depending on the task, this issue may include sensitive information, such as decrypted secret values.
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Ansible | Redhat | * | 2.14.4 (excluding) |
Ansible | Redhat | 2.15.0 (including) | 2.15.9 (excluding) |
Ansible | Redhat | 2.16.0 (including) | 2.16.3 (excluding) |
Enterprise_linux | Redhat | 8.0 (including) | 8.0 (including) |
Enterprise_linux | Redhat | 9.0 (including) | 9.0 (including) |
Red Hat Ansible Automation Platform 2.4 for RHEL 8 | RedHat | ansible-core-1:2.15.9-1.el8ap | * |
Red Hat Ansible Automation Platform 2.4 for RHEL 9 | RedHat | ansible-core-1:2.15.9-1.el9ap | * |
Red Hat Enterprise Linux 8 | RedHat | ansible-core-0:2.16.3-2.el8 | * |
Red Hat Enterprise Linux 9 | RedHat | ansible-core-1:2.14.14-1.el9 | * |
Ansible | Ubuntu | bionic | * |
Ansible | Ubuntu | focal | * |
Ansible | Ubuntu | lunar | * |
Ansible | Ubuntu | mantic | * |
Ansible | Ubuntu | oracular | * |
Ansible | Ubuntu | trusty | * |
Ansible | Ubuntu | trusty/esm | * |
Ansible | Ubuntu | xenial | * |
Ansible-core | Ubuntu | lunar | * |
Ansible-core | Ubuntu | mantic | * |
Ansible-core | Ubuntu | oracular | * |