GHSA-gj5m-m88j-v7c3

Source

https://github.com/advisories/GHSA-gj5m-m88j-v7c3

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/05/GHSA-gj5m-m88j-v7c3/GHSA-gj5m-m88j-v7c3.json

Aliases

• BIT-activemq-2024-32114
• CVE-2024-32114

Published

2024-05-02T09:30:48Z

Modified

2024-05-04T08:11:42.112926Z

Summary

Apache ActiveMQ's default configuration doesn't secure the API web context

Details

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.

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