Loading...
Skip to main content

CVE-2023-33246 — Vulnerability in...

CRITICAL
Actively Exploited

Apache RocketMQ may have remote code execution vulnerability when using update configuration function

Published July 6, 2023Updated October 22, 2025Source: osv

What Should I Do?

Patch Immediately

This vulnerability is confirmed under active exploitation (CISA KEV). Patch within 24-48 hours if possible.

Summary

For RocketMQ versions 5.1.0 and below, under certain conditions, there is a risk of remote command execution.  Several components of RocketMQ, including NameServer, Broker, and Controller, are leaked on the extranet and lack permission verification, an attacker can exploit this vulnerability by using the update configuration function to execute commands as the system users that RocketMQ is running as. Additionally, an attacker can achieve the same effect by forging the RocketMQ protocol content.  To prevent these attacks, users are recommended to upgrade to version 5.1.1 or above for using RocketMQ 5.x or 4.9.6 or above for using RocketMQ 4.x .

Advisory Timeline

  • First published July 6, 2023 (1194 days ago).
  • Last revised October 22, 2025 — 839 days after initial publication.
  • Added to CISA's Known Exploited Vulnerabilities catalog 61 days after publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update org.apache.rocketmq:rocketmq-controller to 5.1.1 or later
<!-- Update pom.xml dependency version to 5.1.1 for org.apache.rocketmq:rocketmq-controller -->
Maven
Update org.apache.rocketmq:rocketmq-namesrv to 4.9.6 or later
<!-- Update pom.xml dependency version to 4.9.6 for org.apache.rocketmq:rocketmq-namesrv -->
Maven
Update org.apache.rocketmq:rocketmq-namesrv to 5.1.1 or later
<!-- Update pom.xml dependency version to 5.1.1 for org.apache.rocketmq:rocketmq-namesrv -->
Maven
Update org.apache.rocketmq:rocketmq-broker to 5.1.1 or later
<!-- Update pom.xml dependency version to 5.1.1 for org.apache.rocketmq:rocketmq-broker -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (4)

Affects 1 ecosystem: maven (3).

PackageEcosystemAffectedFixed In
org.apache.rocketmq:rocketmq-controller
maven
5.0.0, 5.1.05.1.1
org.apache.rocketmq:rocketmq-namesrv
maven
4.0.0-incubating, 4.1.0-incubating, 4.2.0, 4.3.0 (+17 more)4.9.6
org.apache.rocketmq:rocketmq-namesrv
maven
5.0.0, 5.0.0-PREVIEW, 5.1.05.1.1
org.apache.rocketmq:rocketmq-broker
maven
5.0.0, 5.0.0-PREVIEW, 5.1.05.1.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.8 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Frequently Asked Questions

What is CVE-2023-33246?
Apache RocketMQ may have remote code execution vulnerability when using update configuration function This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.8/10).
How do I check if my project is affected by CVE-2023-33246?
CVE-2023-33246 affects org.apache.rocketmq:rocketmq-controller, org.apache.rocketmq:rocketmq-namesrv and org.apache.rocketmq:rocketmq-broker. This vulnerability is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, meaning it is being actively exploited in the wild. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2023-33246 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.8

Exploitation is straightforward and causes maximum impact. Patch immediately.

Known Exploited Vulnerability

This vulnerability is in CISA's Known Exploited Vulnerabilities (KEV) catalog, indicating active exploitation in the wild.

Added to KEV catalog: September 6, 2023

Remediation deadline: September 27, 2023

Also Known As

GHSA-x3cq-8f32-5f63

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies