CVE-2023-33246: Apache RocketMQ Command Execution
Apache RocketMQ · listed in the CISA catalog of actively exploited vulnerabilities since 2023-09-06.
- CVSS v3.1 (CISA ADP)
- 9.8
- critical
- EPSS (exploit probability, 30 days)
- 97%
- higher than 99.8% of all CVEs
- Added to CISA KEV
- 2023-09-06
- US federal due date 2023-09-27
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2023-33246 explained
CVE-2023-33246 is a remote command execution flaw in Apache RocketMQ 5.1.0 and below. NameServer, Broker and Controller components lack permission verification, so an exposed instance can be abused to run commands. CISA lists it as known exploited, and it needs no authentication or user interaction.
Impact
An unauthenticated remote attacker who can reach exposed RocketMQ components can run commands as the system user RocketMQ runs under. The attack uses the update configuration function or forged RocketMQ protocol content. This can lead to full loss of confidentiality, integrity and availability. CISA rates it automatable with total technical impact, so attackers can exploit it at scale. Attackers are known to use it.
Who is affected
The CVE record lists Apache Software Foundation Apache RocketMQ versions ≤ 5.1.0 as affected. Its structured data names no fixed version. The description recommends upgrading to 5.1.1 or above for RocketMQ 5.x, or 4.9.6 or above for RocketMQ 4.x. Check the vendor advisory to confirm the right version for your deployment.
Written with AI from the data on this page and checked against it automatically.
Official description
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 .
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Apache Software Foundation Apache RocketMQAffectedFixed in
- ≤ 5.1.0
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software Foundation Apache RocketMQ |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: lists.apache.org/thread/1s8j2c8kogthtpv3060yddk03zq0pxyp
- CISA's deadline for US federal agencies: 2023-09-27 (passed) – a useful benchmark for everyone else, too.
What to do
- Upgrade RocketMQ 5.x deployments to
5.1.1or above, as the description recommends. - Upgrade RocketMQ 4.x deployments to
4.9.6or above, as the description recommends. - Keep NameServer, Broker and Controller off the internet and restrict access to trusted hosts.
- Run RocketMQ under a low-privilege system account to limit the effect of command execution.
- Review exposed RocketMQ hosts for unexpected configuration changes and other signs of compromise.
- Follow the vendor advisory and CISA's required action to apply mitigations or discontinue use.
The CVE record's structured data names no fixed version, but the description recommends 5.1.1 or above (5.x) and 4.9.6 or above (4.x). Confirm this in the vendor advisory. If you cannot upgrade, follow CISA's required action: apply the vendor's mitigations, or stop using the product if no mitigations are available. Until then, block external access to NameServer, Broker and Controller.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-94 Improper Control of Generation of Code ('Code Injection')
Questions about CVE-2023-33246
- Is CVE-2023-33246 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-09-06, with a US federal due date of 2023-09-27. Whether it is used in ransomware campaigns is unknown.
- Which versions should I upgrade to?
- The description recommends
5.1.1or above for RocketMQ 5.x and4.9.6or above for RocketMQ 4.x. The record lists versions≤ 5.1.0as affected. - Does an attacker need credentials?
- No. The affected components lack permission verification. An attacker who can reach them over the network can run commands as the system user RocketMQ runs under, without credentials or user interaction.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.