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.
References
Configurations
No configuration.
History
No history.
Information
Published : 2024-05-02 09:15
Updated : 2024-05-02 13:27
NVD link : CVE-2024-32114
Mitre link : CVE-2024-32114
CVE.ORG link : CVE-2024-32114
JSON object : View
Products Affected
No product.
CWE
CWE-1188
Initialization of a Resource with an Insecure Default