CVE-2024-32114

Apache ActiveMQ: Jolokia and REST API were not secured with default configuration

Published May 2, 2024 CVSS 3.1 · 8.5 High EPSS 7.1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-1626 Apache ActiveMQ's default configuration doesn't secure the API web context
Github GHSA Github GHSA GHSA-gj5m-m88j-v7c3 Apache ActiveMQ's default configuration doesn't secure the API web context
History
Type Values Removed Values Added
First Time appeared Apache
Apache activemq
CPEs cpe:2.3:a:apache:activemq:*:*:*:*:*:*:*:*
Vendors & Products Apache
Apache activemq
Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Aug 2, 2024, 2:06 AM
Reserved
Apr 11, 2024, 8:12 AM
Status
Analyzed
Published
May 2, 2024, 9:15 AM
Modified
Jun 17, 2026, 7:29 AM
Severity
Important
Public date
May 1, 2024, 12:00 AM