CVE-2024-51988 HTTP API's queue deletion endpoint does not verify that the user has a required permission
Authenticated users with HTTP API access can delete queues without proper configure permissions, leading to unauthorized data modification.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-51988?
CVE-2024-51988 is a medium-severity missing authorization vulnerability in rabbitmq-server, published on 6 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
RabbitMQ is a feature rich, multi-protocol messaging and streaming broker. In affected versions queue deletion via the HTTP API was not verifying the `configure` permission of the user. Users who had all of the following: 1. Valid credentials, 2. Some permissions for the target virtual host & 3. HTTP API access. could delete queues it had no (deletion) permissions for. This issue has been addressed in version 3.12.11 of the open source rabbitMQ release and in versions 1.5.2, 3.13.0, and 4.0.0 of the tanzu release. Users are advised to upgrade. Users unable to upgrade may disable management plugin and use, for example, Prometheus and Grafana for monitoring.
Weakness: CWE-284
Which versions are affected by CVE-2024-51988?
3 open source packages ship an affected version, including rabbit_common and rabbitmq.
| Package | Affected | Fixed in |
|---|---|---|
rabbit_common Hex | From 3.12.7 | 3.12.11 |
rabbit_common Hex | From 3.12.7 | 3.12.11 |
rabbitmq Bitnami | From 3.12.7 | 3.12.11 |
How do I fix CVE-2024-51988?
Upgrade rabbit_common to 3.12.11 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2024-51988 being exploited?
There is no known exploitation of CVE-2024-51988 in the wild and no public exploit code.
Sources
Also known as BIT-rabbitmq-2024-51988, GHSA-pj33-75x5-32j4.