A flaw was found in Ansible Tower, versions 3.6.x before 3.6.2 and 3.5.x before 3.5.3, where enabling RabbitMQ manager by setting it with -e rabbitmq_enable_manager=true exposes the RabbitMQ management interface publicly, as expected. If the default admin user is still active, an attacker could guess the password and gain access to the system.
The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Ansible_tower | Redhat | 3.5.0 (including) | 3.5.3 (excluding) |
| Ansible_tower | Redhat | 3.6.0 (including) | 3.6.2 (excluding) |
| Red Hat Ansible Tower 3.5 for RHEL 7 | RedHat | ansible-tower-35/ansible-tower:3.5.4-1 | * |
| Red Hat Ansible Tower 3.6 for RHEL 7 | RedHat | ansible-tower-36/ansible-tower:3.6.2-1 | * |
Developers often choose default values that leave the product as open and easy to use as possible out-of-the-box, under the assumption that the administrator can (or should) change the default value. However, this ease-of-use comes at a cost when the default is insecure and the administrator does not change it.