Apache Rocketmq vulnerabilities
4 known vulnerabilities affecting apache/rocketmq.
Total CVEs
4
CISA KEV
1
actively exploited
Public exploits
2
Exploited in wild
2
Severity breakdown
CRITICAL2HIGH1MEDIUM1
Vulnerabilities
Page 1 of 1
CVE-2024-23321HIGHCVSS 8.8≥ 4.5.2, < 5.3.02024-07-22
CVE-2024-23321 [HIGH] CWE-200 CVE-2024-23321: For RocketMQ versions 5.2.0 and below, under certain conditions, there is a risk of exposure of sens
For RocketMQ versions 5.2.0 and below, under certain conditions, there is a risk of exposure of sensitive Information to an unauthorized actor even if RocketMQ is enabled with authentication and authorization functions.
An attacker, possessing regular user privileges or listed in the IP whitelist, could potentially acquire the administrator's account
nvd
CVE-2023-37582CRITICALCVSS 9.8ExploitedPoC≤ 4.9.6≥ 5.0.0, ≤ 5.1.12023-07-12
CVE-2023-37582 [CRITICAL] CVE-2023-37582: The RocketMQ NameServer component still has a remote command execution vulnerability as the CVE-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 t
nvd
CVE-2023-33246CRITICALCVSS 9.8KEVPoCfixed in 4.9.6≥ 5.0.0, < 5.1.12023-05-24
CVE-2023-33246 [CRITICAL] CWE-94 CVE-2023-33246: For RocketMQ versions 5.1.0 and below, under certain conditions, there is a risk of remote command e
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 com
nvd
CVE-2019-17572MEDIUMCVSS 5.3≥ 4.2.0, ≤ 4.6.02020-05-14
CVE-2019-17572 [MEDIUM] CWE-22 CVE-2019-17572: In Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by d
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
nvd