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 .
| Score | Percentile |
|---|---|
| 94.39% | 99.97% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 9.8 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-x3cq-8f32-5f63 ↗ |
| CVE | CVE-2023-33246 ↗ |
| CWE id | Name |
|---|---|
| CWE-94 | Improper Control of Generation of Code ('Code Injection') |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| maven | org.apache.rocketmq:rocketmq-broker | >= 5.0.0, < 5.1.1 | 5.1.1 | — |
| maven | org.apache.rocketmq:rocketmq-namesrv | >= 4.0.0, < 4.9.6 | 4.9.6 | — |
| maven | org.apache.rocketmq:rocketmq-controller | >= 5.0.0, < 5.1.1 | 5.1.1 | — |
| maven | org.apache.rocketmq:rocketmq-namesrv | >= 5.0.0, < 5.1.1 | 5.1.1 | — |