A logic flaw exists in Ansible Automation platform. Whenever a private project is created with incorrect credentials, they are logged in plaintext. This flaw allows an attacker to retrieve the credentials from the log, resulting in the loss of confidentiality, integrity, and availability.
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_automation_platform | Redhat | 2.4 (including) | 2.4 (including) |
| Ansible_developer | Redhat | 1.1 (including) | 1.1 (including) |
| Ansible_inside | Redhat | 1.2 (including) | 1.2 (including) |
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | RedHat | automation-eda-controller-0:1.0.1-1.el8ap | * |
| Red Hat Ansible Automation Platform 2.4 for RHEL 9 | RedHat | automation-eda-controller-0:1.0.1-1.el9ap | * |
| Ansible | Ubuntu | bionic | * |
| Ansible | Ubuntu | lunar | * |
| Ansible | Ubuntu | mantic | * |
| Ansible | Ubuntu | trusty | * |
| Ansible | Ubuntu | xenial | * |
| Ansible-core | Ubuntu | lunar | * |
| Ansible-core | Ubuntu | mantic | * |
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: