Threadlinqs IntelligenceStart free

VulnerabilityCVE-2022-41678Published 2023-11-28

CVE-2022-41678 — apache:activemq

highPublic exploit4 PoC reposNuclei template

As of 2025-11-03, CVE-2022-41678 is a HIGH-severity vulnerability in apache:activemq, CVSS v3.1 8.8, EPSS 85.8% (99.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2022-41678 as of 2025-11-03; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
8.8/10High
EPSS
85.8%Higher than 99.7% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
10/10Threadlinqs triage score
Published
Updated 2025-11-03
CVSS v3.1 8.8 (HIGH) · EPSS 85.8% (higher than 99.7% of all scored CVEs) · Priority 10/10 · Published 2023-11-28

Last updated:

What is CVE-2022-41678?

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.

The record classifies CVE-2022-41678 under weakness class CWE-287. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 1087 days ago.

Severity and exploitation probability

CVSS v3.1 base score
8.8 — HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (FIRST)
85.8% probability of exploitation in the next 30 days, higher than 99.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
10/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2023-11-28

Is CVE-2022-41678 being exploited?

Weaponised exploit code for CVE-2022-41678 is publicly available. 4 public proof-of-concept repositories are tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (http/cves/2022/CVE-2022-41678.yaml). It currently carries a trending score of 40 in the Threadlinqs vulnerability feed.

Affected products and versions

  • (vendor unspecified): apache:activemq

How to fix CVE-2022-41678

Vendor advisory: https://activemq.apache.org/security-advisories.data/CVE-2022-41678-announcement.txt. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2022-41678

No threat campaign in the Threadlinqs corpus currently references CVE-2022-41678, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories, ProjectDiscovery Nuclei.

Vendor advisory and patch

Other references