Apache RocketMQ security advisories

Security information for Apache RocketMQ

Reporting

Do you want disclose a potential security issue for Apache RocketMQ? You can read more about the projects’ security policy on their security page, and email your report to the Apache Security Team.

Advisories

This section is experimental: it provides advisories since 2023 and may lag behind the official CVE publications. It may also lack details found on the project security page. If you have any feedback on how you would like this data to be provided, you are welcome to reach out on our public mailinglist or privately on security@apache.org

Unauthorized Exposure of Sensitive Data

CVE-2024-23321 [CVE] [CVE json] [OSV json]

Last updated: 2024-07-22T09:24:05.796Z

Affected

  • Apache RocketMQ from 4.5.2 through 5.2.0

Description

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 and password through specific interfaces. Such an action would grant them full control over RocketMQ, provided they have access to the broker IP address list.

To mitigate these security threats, it is strongly advised that users upgrade to version 5.3.0 or newer. Additionally, we recommend users to use RocketMQ ACL 2.0 instead of the original RocketMQ ACL when upgrading to version Apache RocketMQ 5.3.0.

References

Credits

  • BaoChengZhang (LengJingQiCaiSecurityLab) (finder)

Possible remote code execution when using the update configuration function

CVE-2023-37582 [CVE] [CVE json] [OSV json]

Last updated: 2023-07-12T09:26:16.623Z

Affected

  • Apache RocketMQ from 5.0.0 through 5.1.1
  • Apache RocketMQ through 4.9.6

Description

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.

References

Credits

Possible remote code execution vulnerability when using the update configuration function

CVE-2023-33246 [CVE] [CVE json] [OSV json]

Last updated: 2023-05-24T14:45:21.368Z

Affected

  • Apache RocketMQ through 5.1.0

Description

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 .


References

Credits