Skip to content
Fencer Vulns
high 8.5

CVE-2024-32114 json

Apache ActiveMQ: Jolokia and REST API were not secured with default configuration

published 2024-05-02 2 y ago modified 2026-06-17 4 mo ago also BIT-activemq-2024-32114 , EUVD-2024-1626 , GHSA-gj5m-m88j-v7c3

cvss
8.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
7.1%
EPSS 7.1% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • maven org.apache.activemq:apache-activemq 6.1.2
  • bitnami activemq 6.1.2
  • org.apache.activemq apache-activemq 6.1.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-32114 updated cvss 7.5

activemq-broker: Jolokia and REST API were not secured with default configuration

  • Red Hat A-MQ Clients 2 activemq-broker Red Hat AMQ Broker 7 activemq-broker Red Hat AMQ Clients activemq-broker Red Hat build of Apache Camel for Spring Boot 3 activemq-broker Red Hat Data Grid 8 activemq-broker Red Hat Fuse 7 activemq-broker
    +6 more products
    Red Hat Integration Camel K 1 activemq-broker Red Hat JBoss Data Grid 7 activemq-broker Red Hat JBoss Enterprise Application Platform 7 activemq-broker Red Hat JBoss Enterprise Application Platform 8 activemq-broker Red Hat JBoss Enterprise Application Platform Expansion Pack activemq-broker Red Hat streams for Apache Kafka activemq-broker
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

7.15% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Nuclei template Apache ActiveMQ 6.x < 6.1.2 - Broken Access Control nuclei detection template

CVSS scores

assigned by version score vector
CNA 3.1 8.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OSV 3.1 8.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.activemq:apache-activemq
>=6.0.0, <6.1.2
6.1.2
bitnami activemq
>=6.0.0, <6.1.2
6.1.2

Affected products

  • Apache Software Foundation Apache ActiveMQ
  • apache activemq

Classification

Weakness
  • CWE-1188 Initialization of a Resource with an Insecure Default

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.