CVE-2023-37582 — rocketmq-namesrv
CRITICALCVE-2023-37582 is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.apache.rocketmq:rocketmq-namesrv. 3 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.rocketmq:rocketmq-namesrv — see the affected versions and patch details below.
Apache RocketMQ: Possible remote code execution when using the update configuration function
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-37582.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2023-37582 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.rocketmq:rocketmq-namesrv☕org.apache.rocketmq:rocketmq-namesrvReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
The RocketMQ NameServer component still has a remote command execution vulnerability as the CVE-2023-33246 issue was not completely fixed in version 5.1.1.
When NameServer address are leaked on the extranet and lack permission verification, an attacker can exploit this vulnerability by using the update configuration function on the NameServer component to execute commands as the system users that RocketMQ is running as.
It is recommended for users to upgrade their NameServer version to 5.1.2 or above for RocketMQ 5.x or 4.9.7 or above for RocketMQ 4.x to prevent these attacks.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.rocketmq:rocketmq-namesrv | all versions | 4.9.7org.apache.rocketmq:rocketmq-namesrv:4.9.7 |
| ☕Maven | org.apache.rocketmq:rocketmq-namesrv | ≥ 5.0.0&&< 5.1.2 | 5.1.2org.apache.rocketmq:rocketmq-namesrv:5.1.2 |
Affected Products
rocketmqapacheResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.rocketmq:rocketmq-namesrv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.rocketmq:rocketmq-namesrv to 4.9.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-37582 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2023-37582 in your dependencies?
Find it across Maven, including transitive dependencies.