CVE-2024-32114
Apache ActiveMQ's default configuration doesn't secure the API web context
Impact
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 packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| maven | org.apache.activemq:apache-activemq | >= 6.0.0, < 6.1.2 | 6.1.2 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Apache | Activemq | from 6.0.0 before 6.1.2 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt
- https://github.com/advisories/GHSA-gj5m-m88j-v7c3
- https://nvd.nist.gov/vuln/detail/CVE-2024-32114
- https://github.com/apache/activemq/pull/1201
- https://github.com/apache/activemq/commit/43cc596219b6a8c8b5a54fbda3fb68cb4424f2d0
- https://issues.apache.org/jira/browse/AMQ-9477