CVE-2023-33246
Several components of Apache RocketMQ, including NameServer, Broker, and Controller, are exposed to 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 or achieve the same effect by forging the RocketMQ protocol content.
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 .
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- packetstormsecurity.com/files/173339/Apache-RocketMQ-5.1.0-Arbitrary-Code-Injection.htmlExploitThird Party Advisory
- openwall.com/lists/oss-security/2023/07/12/1Mailing ListThird Party Advisory
- lists.apache.org/thread/1s8j2c8kogthtpv3060yddk03zq0pxypMailing ListVendor Advisory
- vicarius.io/vsociety/posts/rocketmq-rce-cve-2023-33246-33247ExploitThird Party Advisory
- github.com/Malayke/CVE-2023-33246_RocketMQ_RCE_EXPLOITExploit
- github.com/jakabakos/CVE-2023-33246_Apache_RocketMQ_RCEExploit
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-33246Third Party AdvisoryUS Government Resource
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1126 days
- CVSS
- 9.8 CRITICAL
- EPSS (30-day exploit probability)
- 96.6% · top 1% of all CVEs
- Weakness
- CWE-94
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
- 1.Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.