Rocketmq Apache Rocketmq

Do you want an email whenever new security vulnerabilities are reported in Apache Rocketmq?

Known Exploited Apache Rocketmq Vulnerabilities

The following Apache Rocketmq vulnerabilities have been marked by CISA as Known to be Exploited by threat actors.

Title Description Added
Apache RocketMQ Command Execution Vulnerability Several components of Apache RocketMQ, including NameServer, Broker, and Controller, are exposed to 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 or achieve the same effect by forging the RocketMQ protocol content. CVE-2023-33246 September 6, 2023

By the Year

In 2024 there have been 0 vulnerabilities in Apache Rocketmq . Last year Rocketmq had 2 security vulnerabilities published. Right now, Rocketmq is on track to have less security vulnerabilities in 2024 than it did last year.

Year Vulnerabilities Average Score
2024 0 0.00
2023 2 9.80
2022 0 0.00
2021 0 0.00
2020 1 5.30
2019 0 0.00
2018 0 0.00

It may take a day or so for new Rocketmq vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Apache Rocketmq Security Vulnerabilities

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

CVE-2023-37582 9.8 - Critical - July 12, 2023

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.

Code Injection

For RocketMQ versions 5.1.0 and below, under certain conditions, there is a risk of remote command execution

CVE-2023-33246 9.8 - Critical - May 24, 2023

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 .

Code Injection

In Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like

CVE-2019-17572 5.3 - Medium - May 14, 2020

In Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like ../../../../topic2020 is sent from rocketmq-client to the broker, a topic folder will be created in the parent directory in brokers, which leads to a directory traversal vulnerability. Users of the affected versions should apply one of the following: Upgrade to Apache RocketMQ 4.6.1 or later.

Directory traversal

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Apache Rocketmq or by Apache? Click the Watch button to subscribe.

Apache
Vendor

subscribe