{"id":"CVE-2024-51988","aliases":["BIT-rabbitmq-2024-51988","EUVD-2024-3294","GHSA-pj33-75x5-32j4","UBUNTU-CVE-2024-51988"],"status":"published","title":"HTTP API's queue deletion endpoint does not verify that the user has a required permission","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 \u0026 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.","severity":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00362,"percentile":0.30459,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-284"],"published":"2024-11-06T19:15:17Z","modified":"2026-10-28T02:31:09Z","fixes":[{"ecosystem":"Hex","package":"rabbit_common","fixed_in":["3.12.11"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"rabbitmq","fixed_in":["3.12.11"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Hex","package":"rabbit_common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.12.7"},{"fixed":"3.12.11"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"rabbitmq","ranges":[{"type":"SEMVER","events":[{"introduced":"3.12.7"},{"fixed":"3.12.11"}]}]},{"source":"osv","ecosystem":"Hex","package":"rabbit_common","ranges":[{"type":"SEMVER","events":[{"introduced":"3.12.7"},{"fixed":"3.12.11"}]}],"versions":["3.12.10","3.12.7","3.12.8","3.12.9"]}],"products":[{"vendor":"rabbitmq","product":"rabbitmq-server"}],"references":[{"url":"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-pj33-75x5-32j4","tags":["x_refsource_CONFIRM","web","advisory","report"]},{"url":"https://www.rabbitmq.com/docs/prometheus","tags":["x_refsource_MISC","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-51988","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-pj33-75x5-32j4"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/51xxx/CVE-2024-51988.json","tags":["advisory"]},{"url":"https://github.com/rabbitmq/rabbitmq-server","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2024-51988","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-51988","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-51988","title":"HTTP API's queue deletion endpoint does not verify that the user has a required permission","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 \u0026 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.","status":"published","published":"2024-11-06T19:15:17.391Z","modified":"2024-11-06T19:53:22.685Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:34:01.972857Z"}],"euvd":[{"id":"EUVD-2024-3294","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 \u0026 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.","status":"published","published":"2024-11-06T19:15:17Z","modified":"2024-11-06T19:53:22Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-03T00:05:08.721426Z"}],"ghsa":[{"id":"GHSA-pj33-75x5-32j4","title":"RabbitMQ HTTP API's queue deletion endpoint does not verify that the user has a required permission","description":"### Summary\n\nQueue deletion via the HTTP API was not verifying the `configure` permission of the user.\n\n### Impact\n\nUsers who had all of the following:\n\n1. Valid credentials\n2. Some permissions for the target virtual host\n3. HTTP API access \n\ncould delete queues it had no (deletion) permissions for.\n\n### Workarounds\n\nDisable management plugin and use, for example, [Prometheus and Grafana](https://www.rabbitmq.com/docs/prometheus) for monitoring.\n\n### OWASP Classification\n\nOWASP Top10 A01:2021 – Broken Access Control\n","status":"published","published":"2024-11-06T19:55:13Z","modified":"2024-11-07T05:09:46Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"},{"version":"4.0","score":7.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:38:16.477822Z"}],"nvd":[{"id":"CVE-2024-51988","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 \u0026 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.","status":"published","published":"2024-11-06T20:15:06.513Z","modified":"2026-06-17T08:06:45.307Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:10:36.560164Z"}],"osv":[{"id":"CVE-2024-51988","title":"HTTP API's queue deletion endpoint does not verify that the user has a required permission","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 \u0026 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.","status":"published","published":"2024-11-06T19:15:17.391Z","modified":"2026-10-28T02:31:09.248560327Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T15:44:44.032344Z"},{"id":"GHSA-pj33-75x5-32j4","title":"RabbitMQ HTTP API's queue deletion endpoint does not verify that the user has a required permission","description":"### Summary\n\nQueue deletion via the HTTP API was not verifying the `configure` permission of the user.\n\n### Impact\n\nUsers who had all of the following:\n\n1. Valid credentials\n2. Some permissions for the target virtual host\n3. HTTP API access \n\ncould delete queues it had no (deletion) permissions for.\n\n### Workarounds\n\nDisable management plugin and use, for example, [Prometheus and Grafana](https://www.rabbitmq.com/docs/prometheus) for monitoring.\n\n### OWASP Classification\n\nOWASP Top10 A01:2021 – Broken Access Control\n","status":"published","published":"2024-11-06T19:55:13Z","modified":"2025-12-10T00:40:40.894316Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"},{"version":"4.0","score":7.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T15:46:53.244788Z"},{"id":"UBUNTU-CVE-2024-51988","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 \u0026 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.","status":"withdrawn","published":"2024-11-06T20:15:00Z","modified":"2025-07-16T07:47:50.968023Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T16:55:11.182485Z"},{"id":"BIT-rabbitmq-2024-51988","title":"HTTP API's queue deletion endpoint does not verify that the user has a required permission","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 \u0026 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.","status":"published","published":"2024-11-08T07:17:02.8Z","modified":"2025-05-20T10:02:07.006Z","updated_at":"2026-11-02T15:28:35.111822Z"}]}}