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 .

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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 . (CVE-2023-33246)

The version of Apache RocketMQ installed on the remote host is prior to 4.9.6 or 5.1.1. It is, therefore, affected by a remote code execution vulnerability.

  - 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 . (CVE-2023-33246)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
420246	SCA: security update for org.apache.rocketmq:rocketmq-broker, org.apache.rocketmq:rocketmq-controller, org.apache.rocketmq:rocketmq-namesrv (GHSA-x3cq-8f32-5f63)	Tenable Cloud Security	SCA Checks	critical
420246	SCA: security update for org.apache.rocketmq:rocketmq-broker, org.apache.rocketmq:rocketmq-controller, org.apache.rocketmq:rocketmq-namesrv (GHSA-x3cq-8f32-5f63)	Tenable Self-Hosted Container Security	SCA Checks	critical
210953	Apache RocketMQ < 4.9.6 / 5.0.x < 5.1.1 RCE	Nessus	Web Servers	critical

Detections

Analytics

CVE-2023-33246

critical

Tenable Plugins

critical

critical

critical