Most recent entries from all

BIT-rabbitmq-2024-51988 — HTTP API's queue deletion endpoint does not verify that the user has a required permission

Affected: Bitnami: rabbitmq

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.

EUVD-2026-199801

fkie_cve-2024-51988

GHSA-pj33-75x5-32j4 — RabbitMQ HTTP API's queue deletion endpoint does not verify that the user has a required permission

Affected: Hex: rabbit_common

### Summary

Queue deletion via the HTTP API was not verifying the `configure` permission of the user.

### Impact

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.

### Workarounds

Disable management plugin and use, for example, [Prometheus and Grafana](https://www.rabbitmq.com/docs/prometheus) for monitoring.

### OWASP Classification

OWASP Top10 A01:2021 – Broken Access Control

Withdrawn: UBUNTU-CVE-2024-51988

Withdrawn by the publisher.

Affected: Ubuntu:20.04:LTS: rabbitmq-server, Ubuntu:22.04:LTS: rabbitmq-server, Ubuntu:24.04:LTS: rabbitmq-server

WID-SEC-W-2024-3357 — RabbitMQ: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in RabbitMQ ausnutzen, um Sicherheitsvorkehrungen zu umgehen und Daten zu manipulieren.