ID CVE-2023-33246
Summary 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
Vulnerable Configurations
  • cpe:2.3:a:apache:rocketmq:-:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:-:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.9.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.9.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.9.5:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.9.5:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.9.6:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.9.6:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:4.9.7:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:4.9.7:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:5.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:5.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:5.0.0:alpha:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:5.0.0:alpha:*:*:*:*:*:*
  • cpe:2.3:a:apache:rocketmq:5.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:rocketmq:5.1.0:*:*:*:*:*:*:*
CVSS
Base: None
Impact:
Exploitability:
CWE CWE-94
CAPEC
  • Code Injection
    An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion in that code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
  • Manipulating User-Controlled Variables
    This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An attacker can override environment variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the attacker can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.
Access
VectorComplexityAuthentication
Impact
ConfidentialityIntegrityAvailability
Last major update 12-07-2023 - 12:15
Published 24-05-2023 - 15:15
Last modified 12-07-2023 - 12:15
Back to Top