dbcve.org
RocketmqApplication · Apache

CVE-2024-23321

HIGH · 8.8 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 5.3.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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
For RocketMQ versions 5.2.0 and below, under certain conditions, there is a risk of exposure of sensitive Information to an unauthorized actor even if RocketMQ is enabled with authentication and authorization functions. An attacker, possessing regular user privileges or listed in the IP whitelist, could potentially acquire the administrator's account and password through specific interfaces. Such an action would grant them full control over RocketMQ, provided they have access to the broker IP address list. To mitigate these security threats, it is strongly advised that users upgrade to version 5.3.0 or newer. Additionally, we recommend users to use RocketMQ ACL 2.0 instead of the original RocketMQ ACL when upgrading to version Apache RocketMQ 5.3.0.

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

RocketMQ versions 5.2.0 and below contain an authentication bypass vulnerability where attackers with regular user privileges or IP whitelist access can exploit specific interfaces to acquire administrator credentials, gaining full control over the RocketMQ broker even when authentication and authorization are enabled.

MitigationUpgrade to RocketMQ version 5.3.0 or newer and migrate to ACL 2.0 for improved access control. Also review broker access logs for indicators of compromise.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RocketmqApplication
Affected:>= 4.5.2, < 5.3.0

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
High
Integrity
High
Availability
High

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

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. Identify RocketMQ installation and version
    Check the version file in the RocketMQ installation directory (e.g., run `cat ${ROCKETMQ_HOME}/LICENSE` or check `bin/rocketmq` version output). Alternatively, check pom.xml if built from source.
    Affected if The installed version is 4.5.2 or higher but lower than 5.3.0
  2. Verify the Namesrv and Broker process status
    Check if RocketMQ Namesrv and Broker processes are running using commands like `ps -ef | grep rocketmq` or by querying the JMX/RPC ports typically on ports 9876 (namesrv) and 10911 (broker).
    Affected if RocketMQ services are exposed and running on network-accessible ports
  3. Confirm authentication is enabled
    Inspect the broker configuration file (typically `confBroker.conf` or `broker.conf`) for `aclEnable=true` or check for the presence of `plain_acl.yml` or `acl.yml` configuration files in the conf directory.
    Affected if Authentication and authorization are configured but the version is in the affected range (the vulnerability bypasses even enabled auth)
  4. Review broker access logs for credential acquisition attempts
    Examine broker logs (in `logs/rocketmqlogs/` directory) for unusual API calls to interfaces that may grant admin credentials, particularly look for requests from non-admin users to privileged endpoints.
    Affected if Logs show requests from regular users or whitelisted IPs accessing admin-privileged interfaces, or unexpected credential generation events

You are affected if RocketMQ version is 4.5.2 or higher but lower than 5.3.0 and the broker is network-accessible, regardless of whether authentication is enabled.

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
Upgrade available Upgrade to 5.3.0 or later
Fixed in 5.3.0
Interim mitigation

Upgrade to RocketMQ version 5.3.0 or newer and migrate to ACL 2.0 for improved access control. Also review broker access logs for indicators of compromise.

Recommended fix High confidence

Apache RocketMQ 5.3.0 or later

  1. Stop all RocketMQ services (controllers and brokers) before upgrading
  2. Back up existing RocketMQ configuration files and data directories
  3. Upgrade RocketMQ to version 5.3.0 or newer using the appropriate installation method for your environment
  4. Verify the upgrade was successful by checking the RocketMQ version
  5. After upgrade, consider migrating to ACL 2.0 as recommended in the official security advisory for enhanced authorization
  6. Restart RocketMQ services and verify normal operation
Caveat Review release notes for any breaking changes between your current version and 5.3.0; ACL 2.0 has different configuration syntax than original ACL

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

Fix this in Rocketmq Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23321 — 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-23321 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