Apache ActiveMQ's default configuration doesn't secure the API web context
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.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.activemq:apache-activemq | >= 6.0.0, < 6.1.2 | 6.1.2 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-32114
- https://github.com/apache/activemq/pull/1201
- https://github.com/apache/activemq/commit/43cc596219b6a8c8b5a54fbda3fb68cb4424f2d0
- https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt
- https://github.com/apache/activemq
- https://issues.apache.org/jira/browse/AMQ-9477
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-1188- Platform
- Java / Kotlin (Maven)
- Package
org.apache.activemq:apache-activemq- Disclosed
- 02.05.2024
- Updated
- 11.10.2026 12:21
Sources and licenses
OSV / GitHub Advisory Database - GHSA-gj5m-m88j-v7c3 - CC BY 4.0
Vulnerability history: org.apache.activemq:apache-activemq
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 15
- First → latest
- 05.2022 06.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 8
- Medium 7
Disclosures per year
- 2022: 1
- 2023: 1
- 2024: 1
- 2025: 0
- 2026: 12
-
Apache ActiveMQ's default configuration doesn't secure the API web context this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.