CVE-2022-41678

Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. <br /> <br /> In details, in ActiveMQ configurations, jetty allows<br /> org.jolokia.http.AgentServlet to handler request to /api/jolokia<br /> <br /> org.jolokia.http.HttpRequestHandler#handlePostRequest is able to<br /> create JmxRequest through JSONObject. And calls to<br /> org.jolokia.http.HttpRequestHandler#executeRequest.<br /> <br /> Into deeper calling stacks,<br /> org.jolokia.handler.ExecHandler#doHandleRequest can be invoked<br /> through refection. This could lead to RCE through via<br /> various mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.<br /> <br /> 1 Call newRecording.<br /> <br /> 2 Call setConfiguration. And a webshell data hides in it.<br /> <br /> 3 Call startRecording.<br /> <br /> 4 Call copyTo method. The webshell will be written to a .jsp file.<br /> <br /> The mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.<br /> 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.<br />