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 .
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
| Link | Tags |
|---|---|
| https://lists.apache.org/thread/1s8j2c8kogthtpv3060yddk03zq0pxyp | vendor advisory mailing list |
| http://packetstormsecurity.com/files/173339/Apache-RocketMQ-5.1.0-Arbitrary-Code-Injection.html | third party advisory vdb entry exploit |
| http://www.openwall.com/lists/oss-security/2023/07/12/1 | third party advisory mailing list |
| https://www.vicarius.io/vsociety/posts/rocketmq-rce-cve-2023-33246-33247 | exploit third party advisory |
| https://github.com/Malayke/CVE-2023-33246_RocketMQ_RCE_EXPLOIT | exploit |
| https://github.com/jakabakos/CVE-2023-33246_Apache_RocketMQ_RCE | exploit |