CVE-2024-32114: Apache ActiveMQ: Jolokia and REST API were not secured with default configuration
In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).
To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping"> <property name="constraint" ref="securityConstraint" /> <property name="pathSpec" value="/" /> </bean>
Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-32114?
CVE-2024-32114 has a high severity due to the lack of authentication for the Jolokia JMX REST API and Message REST API.
How do I fix CVE-2024-32114?
To fix CVE-2024-32114, configure security settings to require authentication for the API endpoints in Apache ActiveMQ.
Which versions are affected by CVE-2024-32114?
CVE-2024-32114 affects Apache ActiveMQ versions from 6.0.0 to 6.1.2.
What type of attack can be conducted due to CVE-2024-32114?
CVE-2024-32114 allows unauthorized users to interact with the message broker and potentially compromise broker integrity.
Is there a patch available for CVE-2024-32114?
Yes, a patch addressing CVE-2024-32114 is expected in forthcoming updates of Apache ActiveMQ.