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.
History

No history.

cve-icon MITRE Information

Status: PUBLISHED

Assigner: apache

Published: 2024-05-02T08:29:18.219Z

Updated: 2024-06-04T17:50:57.920Z

Reserved: 2024-04-11T08:12:15.896Z


Link: CVE-2024-32114

JSON object: View

cve-icon NVD Information

Status : Awaiting Analysis

Published: 2024-05-02T09:15:06.990

Modified: 2024-05-02T13:27:25.103


Link: CVE-2024-32114

JSON object: View

cve-icon Redhat Information

No data.

CWE