CVE-2023-33246
CRITICALCVE-2023-33246 is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.apache.rocketmq:rocketmq-broker. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-09-06) — treat it as actively exploited and patch now. O3 Security confirms whether CVE-2023-33246 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache RocketMQ: Possible remote code execution vulnerability when using the update configuration function
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-09-06. Federal agencies were required to remediate by 2023-09-27.
- 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.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2023-33246.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-33246 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 368,770 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.rocketmq:rocketmq-broker☕org.apache.rocketmq:rocketmq-namesrv☕org.apache.rocketmq:rocketmq-controller☕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
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 .
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕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 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
For RocketMQ versions 5.1.0 and below, under certain conditions, there i…
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-broker. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.rocketmq:rocketmq-broker to 5.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-33246 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2023-33246 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2023-33246. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-33246 in your dependencies?
O3 detects CVE-2023-33246 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.