HighGHSA-53v4-42fg-g287BIT-activemq-2022-41678CVE-2022-41678

Apache ActiveMQ Deserialization of Untrusted Data vulnerability

Published 28 Nov 2023 · Updated 4 Nov 2025

Is your project on an affected org.apache.activemq:apache-activemq?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<5.16.6
Fixed in
5.16.6
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.activemq:apache-activemq -DdepVersion=5.16.6 -DforceVersion=true
Affected
>=5.17.0 <5.17.4
Fixed in
5.17.4
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.activemq:apache-activemq -DdepVersion=5.17.4 -DforceVersion=true

Details

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 is able to invoke through refection.

And then, RCE is able to be achieved via 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.

Is GHSA-53v4-42fg-g287 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.activemq:apache-activemq, and gives you the command that fixes it.

More advisories for org.apache.activemq:apache-activemq

  • HighCVE-2026-50734Apache ActiveMQ Client, Apache ActiveMQ, Apache ActiveMQ All has a Memory Allocation with Excessive Size Value vulnerability · 30 Jun 2026
  • HighCVE-2026-50750Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All have a Denial of Service via Out of Memory vulnerability · 30 Jun 2026
  • HighCVE-2026-53917Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ Client, Apache ActiveMQ Broker have Memory Allocation with Excessive Size Value vulnerability · 30 Jun 2026
  • HighCVE-2026-49877Apache ActiveMQ Improper Authorization vulnerability · 30 Jun 2026
  • HighCVE-2026-49434Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All have an Improper Input Validation vulnerability · 30 Jun 2026
  • HighCVE-2026-54475Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ have a Missing Authorization vulnerability · 30 Jun 2026
All 23 advisories for org.apache.activemq:apache-activemq

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.