CVE-2024-32114
Published: 02 May 2024
Summary
CVE-2024-32114 is a high-severity Initialization of a Resource with an Insecure Default (CWE-1188) vulnerability in Apache Activemq. Its CVSS base score is 8.5 (High).
Operationally, ranked in the top 1.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
In Apache ActiveMQ 6.x the default configuration leaves the API web context unprotected, exposing both the Jolokia JMX REST API and the Message REST API without any authentication requirement. This affects the broker's embedded Jetty server and stems from an incomplete security-constraint mapping in the shipped conf/jetty.xml file (CWE-1188).
An attacker with network adjacency to the broker can therefore invoke arbitrary JMX operations through Jolokia or use the Message REST API to produce, consume, purge, or delete destinations and messages, all without credentials. The CVSS 8.5 vector reflects the combination of adjacent-network access, low attack complexity, and high impact on confidentiality and availability.
The project advisory directs users either to edit conf/jetty.xml to add a securityConstraintMapping that covers the root path or to upgrade directly to ActiveMQ 6.1.2, where authentication is enabled by default for these endpoints.
EPSS currently stands at 0.6727 with a recorded peak of 0.7414; the values indicate sustained moderate exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-1626
Vulnerability 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…
more
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.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires documented secure initialization practices and avoidance of insecure defaults in configuration baselines.
Reviewing and updating baseline when components are installed or upgraded prevents initialization with insecure defaults.
Requiring explicit configuration to minimal functionality overrides insecure defaults that would otherwise enable excess capabilities.
Tailoring replaces or augments insecure default initializations with system-specific values and compensating controls before deployment.
Central configuration overrides or replaces insecure default initializations that would otherwise be left unchanged on each system.
SCRM practices during acquisition and configuration management address insecure default initializations shipped by vendors.
Scans detect resources initialized with insecure defaults that create exploitable conditions.
Instruction on secure initialization of security controls prevents leaving resources with insecure defaults after installation.