Tower: special characters in RabbitMQ passwords causes web socket 500 error
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Tower | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Ansible Tower 3.5 for RHEL 7 | |||
| ansible-tower-35/ansible-tower:3.5.4-1 | cpe:/a:redhat:ansible_tower:3.5::el7 | RHSA-2019:4242 | 2019-12-16T00:00:00Z |
| Red Hat Ansible Tower 3.6 for RHEL 7 | |||
| ansible-tower-36/ansible-tower:3.6.2-1 | cpe:/a:redhat:ansible_tower:3.6::el7 | RHSA-2019:4243 | 2019-12-16T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-8963 | A flaw was found in Ansible Tower, versions 3.6.x before 3.6.2 and 3.5.x before 3.5.4, when /websocket is requested and the password contains the '#' character. This request would cause a socket error in RabbitMQ when parsing the password and an HTTP error code 500 and partial password disclose will occur in plaintext. An attacker could easily guess some predictable passwords or brute force the password. |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.108% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.