Several components of Apache RocketMQ, including NameServer, Broker, and Controller, are exposed to the extranet and lack permission verification. Threat actors could exploit this vulnerability to execute arbitrary commands as the system users that RocketMQ is running. An attacker can trigger the flaw by using the update configuration function or by forging the RocketMQ protocol content
The vulnerability impacts Apache RocketMQ 5.1.0 and below, users are recommended to upgrade to version 5.1.1 above for using RocketMQ 5.x or 4.9.6 above for using RocketMQ 4.x .
The Apache’s advisory was published on May, but CISA added the issue to the Known Exploited Vulnerabilities Catalog after cybersecurtiy firm VulnCheck published technical details for the vulnerability.
“CVE-2023-33246 is an easy to exploit vulnerability affecting Apache RocketMQ. The vulnerability allows a remote and unauthenticated attacker to update the RocketMQ broker configuration in order to abuse a command injection.” reads the analysis published by VulnCheck. “Juniper Networks has reported exploitation of this issue has been ongoing since June 2023.”
The researchers pointed out that exploitation occurs via a custom remoting protocol to the RocketMQ broker ports (by default 10909 and 10911). Both Shodan or Censys are not able to detect this protocol, making it hard to determine the actual scope of vulnerable systems in the wild.
The researchers explained that CVE-2023-33246 is only associated with one botnet, however, they believe that at least a few active threat actors are actively exploiting the issue in the wild. Experts recommend removing RocketMQ instance from the internet and examining the broker configuration for signs of exploitation.
According to Binding Operational Directive (BOD) 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities, FCEB agencies have to address the identified vulnerabilities by the due date to protect their networks against attacks exploiting the flaws in the catalog.
Experts recommend also private organizations review the Catalog and address the vulnerabilities in their infrastructure.
CISA orders federal agencies to fix this flaw by September 27, 2023.
(SecurityAffairs – hacking, CISA)