An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6 and RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12, and 1.7.x before 1.7.7. MQTT (MQ Telemetry Transport) connection authentication with a username/password pair succeeds if an existing username is provided but the password is omitted from the connection request. Connections that use TLS with a client-provided certificate are not affected.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Rabbitmq | Pivotal_software | 3.5.4 (including) | 3.5.4 (including) |
| Rabbitmq | Pivotal_software | 3.5.5 (including) | 3.5.5 (including) |
| Rabbitmq | Pivotal_software | 3.5.7 (including) | 3.5.7 (including) |
| Rabbitmq | Pivotal_software | 3.6.0 (including) | 3.6.0 (including) |
| Rabbitmq | Pivotal_software | 3.6.1 (including) | 3.6.1 (including) |
| Rabbitmq | Pivotal_software | 3.6.2 (including) | 3.6.2 (including) |
| Rabbitmq | Pivotal_software | 3.6.3 (including) | 3.6.3 (including) |
| Rabbitmq | Pivotal_software | 3.6.4 (including) | 3.6.4 (including) |
| Rabbitmq | Pivotal_software | 3.6.5 (including) | 3.6.5 (including) |
| Rabbitmq | Vmware | 3.0.0 (including) | 3.0.0 (including) |
| Rabbitmq | Vmware | 3.0.1 (including) | 3.0.1 (including) |
| Rabbitmq | Vmware | 3.0.2 (including) | 3.0.2 (including) |
| Rabbitmq | Vmware | 3.0.3 (including) | 3.0.3 (including) |
| Rabbitmq | Vmware | 3.0.4 (including) | 3.0.4 (including) |
| Rabbitmq | Vmware | 3.1.0 (including) | 3.1.0 (including) |
| Rabbitmq | Vmware | 3.1.1 (including) | 3.1.1 (including) |
| Rabbitmq | Vmware | 3.1.2 (including) | 3.1.2 (including) |
| Rabbitmq | Vmware | 3.1.3 (including) | 3.1.3 (including) |
| Rabbitmq | Vmware | 3.1.4 (including) | 3.1.4 (including) |
| Rabbitmq | Vmware | 3.1.5 (including) | 3.1.5 (including) |
| Rabbitmq | Vmware | 3.2.0 (including) | 3.2.0 (including) |
| Rabbitmq | Vmware | 3.2.1 (including) | 3.2.1 (including) |
| Rabbitmq | Vmware | 3.2.2 (including) | 3.2.2 (including) |
| Rabbitmq | Vmware | 3.2.3 (including) | 3.2.3 (including) |
| Rabbitmq | Vmware | 3.2.4 (including) | 3.2.4 (including) |
| Rabbitmq | Vmware | 3.3.0 (including) | 3.3.0 (including) |
| Rabbitmq | Vmware | 3.3.1 (including) | 3.3.1 (including) |
| Rabbitmq | Vmware | 3.3.2 (including) | 3.3.2 (including) |
| Rabbitmq | Vmware | 3.3.3 (including) | 3.3.3 (including) |
| Rabbitmq | Vmware | 3.3.4 (including) | 3.3.4 (including) |
| Rabbitmq | Vmware | 3.3.5 (including) | 3.3.5 (including) |
| Rabbitmq | Vmware | 3.4.0 (including) | 3.4.0 (including) |
| Rabbitmq | Vmware | 3.4.1 (including) | 3.4.1 (including) |
| Rabbitmq | Vmware | 3.4.2 (including) | 3.4.2 (including) |
| Rabbitmq | Vmware | 3.4.3 (including) | 3.4.3 (including) |
| Rabbitmq | Vmware | 3.4.4 (including) | 3.4.4 (including) |
| Rabbitmq | Vmware | 3.5.0 (including) | 3.5.0 (including) |
| Rabbitmq | Vmware | 3.5.1 (including) | 3.5.1 (including) |
| Rabbitmq | Vmware | 3.5.2 (including) | 3.5.2 (including) |
| Rabbitmq | Vmware | 3.5.3 (including) | 3.5.3 (including) |
| Rabbitmq | Vmware | 3.5.6 (including) | 3.5.6 (including) |
| Rabbitmq-server | Ubuntu | precise | * |
| Rabbitmq-server | Ubuntu | trusty | * |
| Rabbitmq-server | Ubuntu | upstream | * |
| Rabbitmq-server | Ubuntu | xenial | * |
| Rabbitmq-server | Ubuntu | yakkety | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: