Skip to content

Apache RocketMQ may have remote code execution vulnerability when using update configuration function

Critical severity GitHub Reviewed Published Jul 6, 2023 to the GitHub Advisory Database • Updated Nov 7, 2023

Package

maven org.apache.rocketmq:rocketmq-broker (Maven)

Affected versions

>= 5.0.0, < 5.1.1

Patched versions

5.1.1
maven org.apache.rocketmq:rocketmq-controller (Maven)
>= 5.0.0, < 5.1.1
5.1.1
maven org.apache.rocketmq:rocketmq-namesrv (Maven)
>= 4.0.0, < 4.9.6
>= 5.0.0, < 5.1.1
4.9.6
5.1.1

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

Published by the National Vulnerability Database May 24, 2023
Published to the GitHub Advisory Database Jul 6, 2023
Reviewed Jul 6, 2023
Last updated Nov 7, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

96.987%
(100th percentile)

Weaknesses

CVE ID

CVE-2023-33246

GHSA ID

GHSA-x3cq-8f32-5f63

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.