Homepage
About Snyk

org.apache.rocketmq:rocketmq-broker@4.5.2 vulnerabilities

Go back to all versions of this package
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the org.apache.rocketmq:rocketmq-broker package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • M
Credential Exposure

org.apache.rocketmq:rocketmq-broker is a distributed messaging and streaming platform.

Affected versions of this package are vulnerable to Credential Exposure. A low-privileged user or one with a whitelisted IP address, who has access to the broker IP address list, can gain access to the credentials for an administrator account even if authentication and authorization are in use.

How to fix Credential Exposure?

Upgrade org.apache.rocketmq:rocketmq-broker to version 5.3.0 or higher.

[4.5.2,5.3.0)
  • H
Arbitrary Code Injection

org.apache.rocketmq:rocketmq-broker is a distributed messaging and streaming platform.

Affected versions of this package are vulnerable to Arbitrary Code Injection. 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.

How to fix Arbitrary Code Injection?

Upgrade org.apache.rocketmq:rocketmq-broker to version 4.9.6, 5.1.1 or higher.

[,4.9.6) [5.0.0,5.1.1)
  • H
Directory Traversal

org.apache.rocketmq:rocketmq-broker is a distributed messaging and streaming platform.

Affected versions of this package are vulnerable to Directory Traversal. 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.

How to fix Directory Traversal?

Upgrade org.apache.rocketmq:rocketmq-broker to version 4.6.1 or higher.

[4.2.0,4.6.1)
Go back to all versions of this package