Skip to main content
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Unauthenticated RCE in Apache RocketMQ update configuration

IdentifiersCVE-2023-33246CWE-94· Improper Control of Generation of…

CVE-2023-33246 is a remote command execution vulnerability in Apache RocketMQ affecting versions 5.1.0 and earlier, with corresponding 4.x releases addressed in 4.9.6. Under certain conditions, exposed RocketMQ components including NameServer, Broker, and Controller can be reached without adequate permission verification. An attacker can abuse the update configuration function to inject a malicious value, including setting configuration such as rocketmqHome to shell command content, causing RocketMQ to execute attacker-controlled commands as the operating system user running the service. The issue can also be triggered by forging RocketMQ protocol content. Public reporting and observed exploitation show attackers sending crafted RocketMQ protocol requests, including requests invoking configuration update behavior, to achieve command execution and deploy follow-on payloads such as miners or botnet malware.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated remote command execution on vulnerable RocketMQ deployments as the system account running RocketMQ. This can result in full compromise of the RocketMQ host within the privileges of that service account, including malware deployment, persistence, data access, configuration tampering, service disruption, and use of the host for lateral movement or botnet activity. In observed cases, the flaw has been used to download and execute malicious shell scripts and deploy XMRig/DreamBus payloads.

Mitigation

If you can’t patch tonight, do this now.

Do not expose RocketMQ NameServer, Broker, or Controller interfaces directly to the internet. Restrict access to trusted management networks, enforce permission verification/authentication where supported, and block untrusted access to configuration update functionality. Apply network ACLs, firewall rules, and segmentation to limit reachability to RocketMQ service ports. Increase monitoring for crafted RocketMQ protocol requests, unexpected configuration changes, suspicious child processes spawned by RocketMQ, and outbound downloads or shell execution from the RocketMQ service account.

Remediation

Patch, then assume compromise.

Upgrade Apache RocketMQ to a fixed release. For RocketMQ 5.x, upgrade to 5.1.1 or later for CVE-2023-33246 remediation; for RocketMQ 4.x, upgrade to 4.9.6 or later. Because later reporting indicates the original fix was incomplete for the NameServer component and was subsequently tracked as CVE-2023-37582, operators should also ensure NameServer is updated to 5.1.2+ on 5.x or 4.9.7+ on 4.x where applicable. After patching, review systems for signs of prior compromise, as upgrading does not remove attacker persistence or payloads already deployed.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (5 hidden).

VALID 2 / 7 TOTALView more in app
CVE-2023-33246MaturityPoCVerified exploit

This repository is a proof-of-concept exploit for CVE-2023-33246, targeting Apache RocketMQ (version 4.9.1 as per the Maven dependency). The main exploit logic is implemented in 'src/main/java/org/example/Main.java'. The exploit attempts to update the configuration of RocketMQ brokers at three hardcoded IP addresses by injecting a malicious value into the 'rocketmqHome' property. The payload is designed to execute a shell command on the target, which pings a unique domain (chr17sz2vtc0000ymdaggehyuhhyyyyyb.oast.fun) for out-of-band detection of successful command execution. The repository includes standard Java project files and Maven configuration, with the exploit code as the main entry point. No framework is used; this is a standalone Java POC. The attack vector is network-based, requiring access to the RocketMQ broker's management interface.

I5N0rthDisclosed May 30, 2023javaxmlnetwork
CVE-2023-33246_RocketMQ_RCE_EXPLOITMaturityPoCVerified exploit

This repository provides an operational exploit and detection toolkit for CVE-2023-33246, a remote code execution vulnerability in Apache RocketMQ (versions 5.1.0 and below). The main exploit script, 'CVE-2023-33246_RocketMQ_RCE_EXPLOIT.py', crafts and sends a malicious RocketMQ protocol message to a specified broker IP and port (default 10911), injecting arbitrary system commands via the configuration update mechanism. The exploit is executed over a raw TCP connection and can run any command as the RocketMQ service user. The repository also includes 'check.py', a multi-threaded scanner that can check single IPs, files of targets, or CIDR ranges for vulnerable RocketMQ instances, defaulting to port 9876 (nameserver) but configurable. The README provides detailed usage instructions, detection guidance, and mitigation advice. No hardcoded C2 or external endpoints are present in the code, but the exploit is capable of executing arbitrary commands, including those that may reach out to attacker-controlled infrastructure. The repository is structured for both exploitation and detection, with clear separation between the exploit and scanning logic.

MalaykeDisclosed Jun 1, 2023pythonnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationRocketmqapplication
Apache Software FoundationRocketmq-Brokerapplication
Apache Software FoundationRocketmq-Namesrvapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware5

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.