Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Activemq | >= 6.0.0, < 6.1.2 |
Related Weaknesses (CWE)
References
- https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcementVendor Advisory
- https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcementVendor Advisory
FAQ
What is CVE-2024-32114?
CVE-2024-32114 is a vulnerability with a CVSS score of 8.5 (HIGH). 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 wi...
How severe is CVE-2024-32114?
CVE-2024-32114 has been rated HIGH with a CVSS base score of 8.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-32114?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Activemq.