ActivemqApplication · Apache

CVE-2024-32114

HIGH · 8.8 CVSS v3.1 Published 2024-05-02

Fix available

A fix is available. Upgrade to 6.1.2 or later.

See remediation →

95/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · high confidence

Apache ActiveMQ 6.x ships with an unsecured API web context by default, exposing the Jolokia JMX REST API and Message REST API without authentication. This allows unauthenticated remote attackers to interact with the broker, produce/consume messages, and manage destinations.

MitigationUpgrade to Apache ActiveMQ 6.1.2 or later which includes authentication by default, or manually update conf/jetty.xml to add security constraint mappings that enforce authentication on the API endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ActivemqApplication

Affected:>= 6.0.0, < 6.1.2

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Apache ActiveMQ version

Locate the ActiveMQ installation directory and check the version. In the installation root, look for a RELEASE-NOTES file or run: ls -la and check for version markers. Alternatively, check if there's a version file in the lib directory or use any package manager that installed ActiveMQ.

Affected if The installed version is >= 6.0.0 and < 6.1.2
Verify web connector is enabled

Check if the web server is running by examining conf/jetty.xml or conf/jetty-realm.properties. Look for connector configurations that enable HTTP/HTTPS access on ports like 8161 (default web console port).

Affected if The web connector is active and accessible on a network port
Inspect jetty.xml for security constraints

Examine the conf/jetty.xml file and search for security-constraint or constraint mappings. Specifically look for sections that define URL patterns for /api/jolokia or /api/message and whether they have associated security constraint definitions.

Affected if No security-constraint mappings are defined for the /api/* endpoints, or none exist at all
Test unauthenticated API access

Attempt to access the Jolokia endpoint at http://localhost:8161/api/jolokia or the Message REST API at http://localhost:8161/api/message without providing any credentials. Use curl or similar: curl -I http://localhost:8161/api/jolokia

Affected if The endpoints respond with HTTP 200 or 401 (meaning they are reachable) rather than requiring authentication upfront; a successful response without credentials indicates the vulnerability is present
Check for disabled anonymous access in jetty.xml

In conf/jetty.xml, look for security-related configuration sections. Specifically check if ConstraintSecurityHandler or LoginAuthenticator is configured with any form of authentication enforcement. Look for missing <auth-method> or <constraint> definitions.

Affected if No authentication method is explicitly configured for the API web context, leaving it open by default

A user is affected if they are running Apache ActiveMQ version 6.0.0 through 6.1.1 with the web console API accessible without authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 6.1.2 or later

Fixed in 6.1.2

Interim mitigation

Upgrade to Apache ActiveMQ 6.1.2 or later which includes authentication by default, or manually update conf/jetty.xml to add security constraint mappings that enforce authentication on the API endpoints.

Recommended fix High confidence

Apache ActiveMQ 6.1.2

Download Apache ActiveMQ 6.1.2 from the official Apache ActiveMQ distribution (https://activemq.apache.org/download)
Stop the currently running ActiveMQ 6.x instance
Backup the existing ActiveMQ installation directory including conf/ and data/ directories
Extract or install Apache ActiveMQ 6.1.2 to the target location
Copy the backed-up configuration files (especially conf/jetty.xml and any customized configs) to the new installation
Start the ActiveMQ 6.1.2 service
Verify that authentication is now required for the Jolokia JMX REST API and Message REST API endpoints

Caveat Any existing clients or scripts that rely on unauthenticated access to the Jolokia or Message REST APIs will need to be updated with credentials

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Activemq Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h

6.0 hours of engineering $1,060

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-32114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

activemq.apache.orgVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-32114 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-32114?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to 6.1.2 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 7.1%

Affects: Activemq

Remediation

A high-priority fix

Fix this in Activemq 6 hrs · Moderate

Typical engagement from $1,060

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-32114 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References