dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-51988

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RabbitMQ's HTTP API for queue deletion failed to verify the `configure` permission, allowing authenticated users with only basic virtual host access to delete queues they lacked deletion permissions for. This is an authorization bypass in the management API.

MitigationUpgrade to RabbitMQ 3.12.11+, 3.13.0+, or 4.0.0+ (or Tanzu 1.5.2+). If upgrading is not feasible, disable the management plugin and use Prometheus/Grafana for monitoring instead.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check RabbitMQ version
    Run `rabbitmqctl status` or query the management API at `GET /api/overview` and look for the `rabbitmq_version` field
    Affected if Version is before 3.12.11, 3.13.0, or 4.0.0 (or Tanzu before 1.5.2)
  2. Verify management plugin is enabled
    Run `rabbitmq-plugins list` and check if `rabbitmq_management` or `rabbitmq_management_agent` appears as enabled (E*)
    Affected if Management plugin is enabled and RabbitMQ version is vulnerable
  3. Identify users with basic virtual host access
    Query the management API `GET /api/permissions` or run `rabbitmqctl list_permissions` and look for users granted only `.*` or basic access on a vhost without explicit delete permission
    Affected if Users exist with read/write access to a vhost but lack explicit configure permission on specific queues
  4. Check configure permission enforcement on queue deletion
    Use the management API to attempt a DELETE request to `/api/queues/{vhost}/{name}` with a test user who has only basic vhost permissions (read/write) but no configure permission
    Affected if The API accepts the deletion request despite the user lacking configure permission on the queue

You are affected if running a vulnerable RabbitMQ version with the management plugin enabled and users have basic virtual host access without explicit configure permissions on queues.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to RabbitMQ 3.12.11+, 3.13.0+, or 4.0.0+ (or Tanzu 1.5.2+). If upgrading is not feasible, disable the management plugin and use Prometheus/Grafana for monitoring instead.

Recommended fix High confidence

RabbitMQ 3.12.11 (open source) or 1.5.2/3.13.0/4.0.0 (Tanzu)

  1. Identify your RabbitMQ deployment type (open source or Tanzu) and current version
  2. For open source RabbitMQ: upgrade to version 3.12.11 or later
  3. For Tanzu RabbitMQ: upgrade to version 1.5.2, 3.13.0, 4.0.0 or later depending on your Tanzu version track
  4. After upgrade, verify that queue deletion via HTTP API now correctly enforces configure permissions
  5. Alternatively, if upgrade is not immediately feasible: disable the management plugin and use Prometheus with Grafana for monitoring instead
Caveat Standard upgrade considerations apply - review release notes for any breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51988 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51988 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data