A flaw was found in the Ansible Automation Platforms Event-Driven Ansible. In configurations where verbosity is set to debug, inventory passwords are exposed in plain text when starting a rulebook activation. This issue exists for any debug action in a rulebook and also affects Event Streams.
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | RedHat | ansible-rulebook-0:1.0.8-2.el8ap | * |
| Red Hat Ansible Automation Platform 2.4 for RHEL 9 | RedHat | ansible-rulebook-0:1.0.8-2.el9ap | * |
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | RedHat | ansible-rulebook-0:1.1.4-2.el8ap | * |
| Red Hat Ansible Automation Platform 2.5 for RHEL 9 | RedHat | ansible-rulebook-0:1.1.4-2.el9ap | * |
Debug messages are messages that help troubleshoot an issue by revealing the internal state of the system. For example, debug data in design can be exposed through internal memory array dumps or boot logs through interfaces like UART via TAP commands, scan chain, etc. Thus, the more information contained in a debug message, the easier it is to debug. However, there is also the risk of revealing information that could help an attacker either decipher a vulnerability, and/or gain a better understanding of the system. Thus, this extra information could lower the “security by obscurity” factor. While “security by obscurity” alone is insufficient, it can help as a part of “Defense-in-depth”.