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

Tue, 11 Feb 2025 17:00:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache activemq
CPEs cpe:2.3:a:apache:activemq:*:*:*:*:*:*:*:*
Vendors & Products Apache
Apache activemq

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2024-08-02T02:06:44.047Z

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

Link: CVE-2024-32114

cve-icon Vulnrichment

Updated: 2024-08-02T02:06:44.047Z

cve-icon NVD

Status : Analyzed

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

Modified: 2025-02-11T16:31:00.073

Link: CVE-2024-32114

cve-icon Redhat

Severity : Important

Publid Date: 2024-05-01T00:00:00Z

Links: CVE-2024-32114 - Bugzilla