Loading vulnerability…
CVE-2023-37582 is a remote command execution vulnerability in the Apache RocketMQ NameServer component. It exists because the fix for CVE-2023-33246 was incomplete, leaving the NameServer still exploitable in affected versions. When a NameServer is exposed on the extranet and lacks permission verification, an attacker can abuse the NameServer update configuration function to inject and execute commands. Successful exploitation results in command execution as the operating system user account running RocketMQ. Reported affected versions include RocketMQ 5.0.0 through 5.1.1 and RocketMQ 4.x prior to 4.9.7.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Python proof-of-concept (PoC) exploit for CVE-2023-37582, a remote code execution vulnerability in Apache RocketMQ. The script defines a hex-encoded payload, connects to a specified IP address and port (default 9876), sends the payload, and analyzes the response to determine if the target is vulnerable. The script prints the target's IP, port, and RocketMQ version if the vulnerability is present. The code is straightforward, with all logic contained in a single file, and is intended for testing the presence of the vulnerability on accessible RocketMQ instances.
This repository contains a proof-of-concept exploit for CVE-2023-37582, an arbitrary file write vulnerability in the Apache RocketMQ nameserver. The main file, 'CVE-2023-37582.py', is a Python script that connects to a RocketMQ nameserver over TCP (default port 9876) and sends a specially crafted request to abuse the UPDATE_NAMESRV_CONFIG functionality. By default, it writes a file to '/tmp/pwned' on the target server, but the payload can be modified to write arbitrary content or files, such as SSH keys or cronjobs. The exploit demonstrates the vulnerability by showing the nameserver's configuration before and after the attack. The repository also includes a README with setup instructions for a local RocketMQ environment using Docker, and a standard Apache 2.0 license file. The exploit is a standalone script, not part of a larger framework, and is intended for demonstration and security research purposes only.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution vulnerability in Apache RocketMQ NameServer affecting the exposed RocketMQ 4.3.2 instance discussed in the report.
Critical remote command execution vulnerability in Apache RocketMQ NameServer that persisted after the initial CVE-2023-33246 fix; exploitation is possible via the NameServer update configuration function when exposed externally without permission verification.
Remote Code Execution vulnerability in the Apache RocketMQ NameServer component, exploitable via the update configuration function under certain exposure/permission conditions.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.