RabbitMQ 3.12 Queue Deletion Auth Bypass
CVE-2024-51988 Published on November 6, 2024
HTTP API's queue deletion endpoint does not verify that the user has a required permission
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.
Vulnerability Analysis
CVE-2024-51988 is exploitable with network access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality, a high impact on integrity, and no impact on availability.
Weakness Type
What is an Authorization Vulnerability?
The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CVE-2024-51988 has been classified to as an Authorization vulnerability or weakness.
Products Associated with CVE-2024-51988
Want to know whenever a new CVE is published for Pivotal Software Rabbitmq? stack.watch will email you.
Affected Versions
rabbitmq-server:- Version Open source RabbitMQ: >= 3.12.7, < 3.12.11 is affected.
- Version Tanzu RabbitMQ: >= 2.0.0, < 3.13.0 is affected.
- Version Tanzu RabbitMQ: < 1.5.2 is affected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.