A flaw was found in Ansible, where sensitive information stored in Ansible Vault files can be exposed in plaintext during the execution of a playbook. This occurs when using tasks such as include_vars to load vaulted variables without setting the no_log: true parameter, resulting in sensitive data being printed in the playbook output or logs. This can lead to the unintentional disclosure of secrets like passwords or API keys, compromising security and potentially allowing unauthorized access or actions.
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 Execution Environments | RedHat | ansible-automation-platform/ansible-builder-rhel8:1.2.0-91 | * |
| Ansible Automation Platform Execution Environments | RedHat | ansible-automation-platform/ansible-builder-rhel9:3.0.1-95 | * |
| Ansible Automation Platform Execution Environments | RedHat | ansible-automation-platform/ee-29-rhel8:2.9.27-32 | * |
| Ansible Automation Platform Execution Environments | RedHat | ansible-automation-platform/ee-minimal-rhel8:2.17.6-1 | * |
| Ansible Automation Platform Execution Environments | RedHat | ansible-automation-platform/ee-minimal-rhel9:2.17.6-2 | * |
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: