CVE-2024-32114
Last modified
CVE-2024-32114 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. . EPSS estimates a 6.92% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Activemq | >= 6.0.0, < 6.1.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-32114?
How severe is CVE-2024-32114?
How do I fix CVE-2024-32114?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-32109Cross-Site Request Forgery (CSRF) vulnerability in Julien Be…4.3
- CVE-2024-3211The Shopping Cart & eCommerce Store plugin for WordPress is …8.8
- CVE-2024-32110Cross-Site request forgery (CSRF) vulnerability in Magepeopl…4.3
- CVE-2024-32111Improper Limitation of a Pathname to a Restricted Directory …5
- CVE-2024-32112Cross-Site Request Forgery (CSRF) vulnerability in Leadinfo …4.3
- CVE-2024-32113Improper Limitation of a Pathname to a Restricted Directory …9.8
- CVE-2024-32115A relative path traversal vulnerability [CWE-23] in Fortinet…5.5
- CVE-2024-32116Multiple relative path traversal vulnerabilities [CWE-23] in…6
- CVE-2024-32117An improper limitation of a pathname to a restricted directo…4.9
- CVE-2024-32118Multiple improper neutralization of special elements used in…6.7
- CVE-2024-32119An improper authentication vulnerability [CWE-287] in Fortin…4.8
- CVE-2024-32122A storing passwords in a recoverable format in Fortinet Fort…4.4
Are you affected by CVE-2024-32114?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST