Apache ActiveMQ's default configuration doesn't secure the API web context
GHSA-gj5m-m88j-v7c3 · BIT-activemq-2024-32114 · CVE-2024-32114
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
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:
Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
References
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2024-32114
- WEB https://github.com/apache/activemq/pull/1201
- WEB https://github.com/apache/activemq/commit/43cc596219b6a8c8b5a54fbda3fb68cb4424f2d0
- WEB https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt
- PACKAGE https://github.com/apache/activemq
- WEB https://issues.apache.org/jira/browse/AMQ-9477
Ready to move
Start Securing
Free, no credit card | First findings in minutes