LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41678: Apache ActiveMQ: Insufficient API restrictions on Jolokia allow authenticated users to perform RCE

Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution.  In details, in ActiveMQ configurations, jetty allows org.jolokia.http.AgentServlet to handler request to /api/jolokia org.jolokia.http.HttpRequestHandler#handlePostRequest is able to create JmxRequest through JSONObject. And calls to org.jolokia.http.HttpRequestHandler#executeRequest. Into deeper calling stacks, org.jolokia.handler.ExecHandler#doHandleRequest can be invoked through refection. This could lead to RCE through via various mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11. 1 Call newRecording. 2 Call setConfiguration. And a webshell data hides in it. 3 Call startRecording. 4 Call copyTo method. The webshell will be written to a .jsp file. The mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia. A more restrictive Jolokia configuration has been defined in default ActiveMQ distribution. We encourage users to upgrade to ActiveMQ distributions version including updated Jolokia configuration: 5.16.6, 5.17.4, 5.18.0, 6.0.0.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-41678 is an authenticated remote code execution risk in Apache ActiveMQ’s Jolokia management API. If an attacker already has Jolokia access, insufficient restrictions may allow them to trigger dangerous MBean operations. This is business-relevant where ActiveMQ management endpoints are reachable beyond tightly controlled administrators.

Executive priority

Treat this as a high-priority management-plane hardening issue, especially for externally reachable or broadly accessible ActiveMQ consoles. Prioritize upgrade or Jolokia restriction, then validate that only trusted administrators can reach the management API.

Technical view

ActiveMQ configurations expose Jolokia at /api/jolokia through AgentServlet. After authentication, Jolokia request handling can invoke ExecHandler paths and MBean methods. The advisory describes possible RCE through MBeans, including a Java Flight Recorder deserialization-related path on Java versions above 11.

Likely exposure

Exposure is most likely in Apache ActiveMQ deployments with Jolokia enabled and reachable to authenticated users. Internet-facing, shared-admin, or weakly governed management planes raise urgency. Exact affected version boundaries should be confirmed from Apache’s advisory and installed distribution configuration.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The issue still matters because the described impact is arbitrary code execution after Jolokia authentication, which can turn compromised or over-privileged management credentials into server compromise.

Researcher notes

Evidence comes primarily from Apache’s advisory text. It identifies authenticated Jolokia RCE potential and recommends restrictive Jolokia defaults or disabling Jolokia. The bundle lacks CVSS, KEV, and complete exploit-in-the-wild evidence, so validation should focus on configuration and version confirmation.

Mitigation direction

  • Upgrade ActiveMQ to a distribution with the updated Jolokia configuration.
  • Use Apache-named fixed distributions: 5.16.6, 5.17.4, 5.18.0, or 6.0.0.
  • Disable Jolokia where it is not operationally required.
  • Restrict Jolokia actions and exposed MBeans to the minimum required.
  • Limit management endpoint access to trusted administrative networks only.

Validation and detection

  • Inventory ActiveMQ instances and record distribution versions.
  • Check whether Jolokia is enabled and exposed at /api/jolokia.
  • Review Jolokia authorization configuration for restricted actions and MBean access.
  • Confirm Java runtime version, especially Java versions above 11.
  • Verify upgrade status against Apache, Debian, and vendor advisories where applicable.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-41678 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache ActiveMQorg.apache.activemq:apache-activemq, 0, 5.17.0, 5.18.0, 6.0.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.