First published: Wed May 01 2024(Updated: )
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.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.activemq:apache-activemq | >=6.0.0<6.1.2 | 6.1.2 |
Apache ActiveMQ | >=6.0.0<6.1.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-32114 has a high severity due to the lack of authentication for the Jolokia JMX REST API and Message REST API.
To fix CVE-2024-32114, configure security settings to require authentication for the API endpoints in Apache ActiveMQ.
CVE-2024-32114 affects Apache ActiveMQ versions from 6.0.0 to 6.1.2.
CVE-2024-32114 allows unauthorized users to interact with the message broker and potentially compromise broker integrity.
Yes, a patch addressing CVE-2024-32114 is expected in forthcoming updates of Apache ActiveMQ.