CVSS: 9.8EPSS: 1%CPEs: 2EXPL: 0CVE-2023-37582 – Apache RocketMQ: Possible remote code execution when using the update configuration function
https://notcve.org/view.php?id=CVE-2023-37582
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. • http://www.openwall.com/lists/oss-security/2023/07/12/1 https://lists.apache.org/thread/m614czxtpvlztd7mfgcs2xcsg36rdbnc • CWE-94: Improper Control of Generation of Code ('Code Injection') •
CVSS: 9.8EPSS: 97%CPEs: 2EXPL: 11CVE-2023-33246 – Apache RocketMQ Command Execution Vulnerability
https://notcve.org/view.php?id=CVE-2023-33246
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 . 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. • https://github.com/SuperZero/CVE-2023-33246 https://github.com/Le1a/CVE-2023-33246 https://github.com/I5N0rth/CVE-2023-33246 https://github.com/yizhimanpadewoniu/CVE-2023-33246-Copy https://github.com/3yujw7njai/CVE-2023-33246 https://github.com/Devil0ll/CVE-2023-33246 https://github.com/d0rb/CVE-2023-33246 https://github.com/0xKayala/CVE-2023-33246 https://github.com/hanch7274/CVE-2023-33246 https://github.com/PavilionQ/CVE-2023-33246-mitigation http://packetstormsecurity& • CWE-94: Improper Control of Generation of Code ('Code Injection') •
CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0CVE-2019-17572
https://notcve.org/view.php?id=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 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. En Apache RocketMQ versiones 4.2.0 hasta 4.6.0, cuando la creación automática de temas en el agente está activada por defecto, un tema maligno como "../../../../topic2020" es enviado desde rocketmq-client para el agente, una carpeta de temas será creada en el directorio principal en los agentes, lo que conduce a una vulnerabilidad de salto del directorio. • https://lists.apache.org/thread.html/fdea1c5407da47a17d5522fa149a097cacded1916c1c1534d46edc6d%40%3Cprivate.rocketmq.apache.org%3E https://seclists.org/oss-sec/2020/q2/112 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •