{"id":"CVE-2022-41678","aliases":["BIT-activemq-2022-41678","DEBIAN-CVE-2022-41678","DLA-3936-1","DSA-5798-1","EUVD-2023-2884","GHSA-53v4-42fg-g287","OESA-2023-1925","UBUNTU-CVE-2022-41678","USN-6910-1","USN-7268-1"],"status":"published","title":"Apache ActiveMQ: Insufficient API restrictions on Jolokia allow authenticated users to perform RCE","description":"Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \n\nIn details, in ActiveMQ configurations, jetty allows\norg.jolokia.http.AgentServlet to handler request to /api/jolokia\n\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to\ncreate JmxRequest through JSONObject. And calls to\norg.jolokia.http.HttpRequestHandler#executeRequest.\n\nInto deeper calling stacks,\norg.jolokia.handler.ExecHandler#doHandleRequest can be invoked\nthrough refection. This could lead to RCE through via\nvarious mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\n\n1 Call newRecording.\n\n2 Call setConfiguration. And a webshell data hides in it.\n\n3 Call startRecording.\n\n4 Call copyTo method. The webshell will be written to a .jsp file.\n\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.","severity":{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-12","score":0.85694,"percentile":0.99729,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-287","CWE-502"],"published":"2023-11-28T15:08:38Z","modified":"2026-11-03T06:02:55Z","exploits":[{"source":"pocgithub","id":"mbadanoiu/CVE-2022-41678","title":"mbadanoiu/CVE-2022-41678","date":"2024-11-28","url":"https://github.com/mbadanoiu/CVE-2022-41678"},{"source":"pocgithub","id":"URJACK2025/CVE-2022-41678","title":"URJACK2025/CVE-2022-41678","date":"2025-10-14","url":"https://github.com/URJACK2025/CVE-2022-41678"},{"source":"pocgithub","id":"Catherines77/ActiveMQ-EXPtools","title":"Catherines77/ActiveMQ-EXPtools","date":"2026-04-20","url":"https://github.com/Catherines77/ActiveMQ-EXPtools"},{"source":"nuclei","id":"CVE-2022-41678","title":"Apache ActiveMQ \u003c 5.16.5/5.17.3 - Remote Code Execution","type":"detection template","url":"https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2022/CVE-2022-41678.yaml"}],"fixes":[{"ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","fixed_in":["5.16.6","5.17.4"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"activemq","fixed_in":["5.16.6","5.17.4"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"activemq","fixed_in":["5.17.2+dfsg-2+deb12u1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"activemq","fixed_in":["5.17.6+dfsg-1"],"sources":["osv"]},{"ecosystem":"openEuler:20.03-LTS-SP1","package":"activemq","fixed_in":["5.16.7-1.oe1"],"sources":["osv"]},{"ecosystem":"openEuler:20.03-LTS-SP3","package":"activemq","fixed_in":["5.16.7-1.oe1"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS","package":"activemq","fixed_in":["5.16.7-1.oe2203sp2"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP1","package":"activemq","fixed_in":["5.16.7-1.oe2203sp1"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP2","package":"activemq","fixed_in":["5.16.7-1.oe2203sp2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"activemq","fixed_in":["5.13.2+dfsg-2ubuntu0.1~esm1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"activemq","fixed_in":["5.15.8-2~18.04.1~esm1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"activemq","fixed_in":["5.15.11-1ubuntu0.1~esm1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"activemq","fixed_in":["5.16.1-1ubuntu0.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.6"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.17.0"},{"fixed":"5.17.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"activemq","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.16.6"},{"introduced":"5.17.0"},{"fixed":"5.17.4"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.17.2+dfsg-2+deb12u1"}]}],"versions":["5.17.2+dfsg-2"]},{"source":"osv","ecosystem":"Debian:13","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.17.6+dfsg-1"}]}]},{"source":"osv","ecosystem":"Debian:11","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.1-1+deb11u1"}]}],"versions":["5.16.1-1"],"bundled":2},{"source":"osv","ecosystem":"Debian:12","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.17.2+dfsg-2+deb12u1"}]}],"versions":["5.17.2+dfsg-2"],"bundled":2},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.6"}]}],"versions":["4.1.1","4.1.2","5.0.0","5.1.0","5.10.0","5.10.1","5.10.2","5.11.0","5.11.1","5.11.2","5.11.3","5.11.4","5.12.0","5.12.1","5.12.2","5.12.3","5.13.0","5.13.1","5.13.2","5.13.3","5.13.4","5.13.5","5.14.0","5.14.1","5.14.2","5.14.3","5.14.4","5.14.5","5.15.0","5.15.1","5.15.10","5.15.11","5.15.12","5.15.13","5.15.14","5.15.15","5.15.16","5.15.2","5.15.3","5.15.4","5.15.5","5.15.6","5.15.7","5.15.8","5.15.9","5.16.0","5.16.1","5.16.2","5.16.3","5.16.4","5.16.5","5.2.0","5.3.0","5.3.1","5.3.2","5.4.0","5.4.1","5.4.2","5.4.3","5.5.0","5.5.1","5.6.0","5.7.0","5.8.0","5.9.0","5.9.1"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.17.0"},{"fixed":"5.17.4"}]}],"versions":["5.17.0","5.17.1","5.17.2","5.17.3"]},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.7-1.oe1"}]}]},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP3","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.7-1.oe1"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.7-1.oe2203sp2"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.7-1.oe2203sp1"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP2","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.7-1.oe2203sp2"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.13.2+dfsg-2ubuntu0.1~esm1"}]}],"versions":["5.6.0+dfsg1-4+deb8u1ubuntu1","5.6.0+dfsg1-5","5.13.2+dfsg-2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.8-2~18.04.1~esm1"}]}],"versions":["5.14.5-3","5.15.2-2","5.15.3-2","5.15.8-2~18.04"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.11-1ubuntu0.1~esm1"}]}],"versions":["5.15.10-1","5.15.11-1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.1-1ubuntu0.1"}]}],"versions":["5.16.1-1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.13.2+dfsg-2ubuntu0.1~esm1"}]}],"versions":["5.6.0+dfsg1-4+deb8u1ubuntu1","5.6.0+dfsg1-5","5.13.2+dfsg-2"],"bundled":6},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.8-2~18.04.1~esm1"}]}],"versions":["5.14.5-3","5.15.2-2","5.15.3-2","5.15.8-2~18.04"],"bundled":6},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.11-1ubuntu0.1~esm1"}]}],"versions":["5.15.10-1","5.15.11-1"],"bundled":6},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.1-1ubuntu0.1~esm1"}]}],"versions":["5.16.1-1"],"bundled":6},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.16.1-1ubuntu0.1"}]}],"versions":["5.16.1-1"],"bundled":2}],"products":[{"vendor":"apache","product":"activemq"},{"vendor":"apache software foundation","product":"apache activemq"}],"references":[{"url":"https://activemq.apache.org/security-advisories.data/CVE-2022-41678-announcement.txt","tags":["vendor-advisory","x_transferred","Vendor Advisory","advisory","web","report"]},{"url":"https://lists.apache.org/thread/7g17kwbtjl011mm4tr8bn1vnoq9wh4sl","tags":["vendor-advisory","x_transferred","Mailing List","Vendor Advisory","advisory","web","report"]},{"url":"https://www.openwall.com/lists/oss-security/2023/11/28/1","tags":["x_transferred","web"]},{"url":"https://security.netapp.com/advisory/ntap-20240216-0004/","tags":["x_transferred","web","advisory"]},{"url":"https://lists.debian.org/debian-lts-announce/2024/10/msg00027.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-41678","tags":["web","advisory"]},{"url":"http://www.openwall.com/lists/oss-security/2023/11/28/1","tags":["web"]},{"url":"https://github.com/apache/activemq/pull/958","tags":["web"]},{"url":"https://github.com/apache/activemq/commit/6120169e563b55323352431dfe9ac67a8b4de6c2","tags":["web"]},{"url":"https://security.netapp.com/advisory/ntap-20240216-0004","tags":["web"]},{"url":"https://github.com/apache/activemq/commit/5c8d457d9","tags":["web"]},{"url":"https://github.com/apache/activemq/commit/bf65929fd","tags":["web"]},{"url":"https://github.com/apache/activemq/commit/d8ce1d9ff","tags":["web"]},{"url":"https://github.com/advisories/GHSA-53v4-42fg-g287"},{"url":"https://repo.maven.apache.org/maven2","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/41xxx/CVE-2022-41678.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2022-41678","tags":["advisory"]},{"url":"https://github.com/apache/activemq","tags":["package"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1925","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-41678","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-41678","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-6910-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7268-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2015-7559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-11775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2020-13920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-26117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-46604","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2022-41678","title":"Apache ActiveMQ: Insufficient API restrictions on Jolokia allow authenticated users to perform RCE","description":"Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \n\nIn details, in ActiveMQ configurations, jetty allows\norg.jolokia.http.AgentServlet to handler request to /api/jolokia\n\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to\ncreate JmxRequest through JSONObject. And calls to\norg.jolokia.http.HttpRequestHandler#executeRequest.\n\nInto deeper calling stacks,\norg.jolokia.handler.ExecHandler#doHandleRequest can be invoked\nthrough refection. This could lead to RCE through via\nvarious mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\n\n1 Call newRecording.\n\n2 Call setConfiguration. And a webshell data hides in it.\n\n3 Call startRecording.\n\n4 Call copyTo method. The webshell will be written to a .jsp file.\n\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.\n","status":"published","published":"2023-11-28T15:08:38.338Z","modified":"2025-11-03T21:46:33.574Z","cwes":["CWE-287"],"updated_at":"2026-11-02T14:34:28.038197Z"}],"euvd":[{"id":"EUVD-2023-2884","description":"Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \n\nIn details, in ActiveMQ configurations, jetty allows\norg.jolokia.http.AgentServlet to handler request to /api/jolokia\n\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to\ncreate JmxRequest through JSONObject. And calls to\norg.jolokia.http.HttpRequestHandler#executeRequest.\n\nInto deeper calling stacks,\norg.jolokia.handler.ExecHandler#doHandleRequest can be invoked\nthrough refection. This could lead to RCE through via\nvarious mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\n\n1 Call newRecording.\n\n2 Call setConfiguration. And a webshell data hides in it.\n\n3 Call startRecording.\n\n4 Call copyTo method. The webshell will be written to a .jsp file.\n\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.\n","status":"published","published":"2023-11-28T15:08:38Z","modified":"2025-11-03T21:46:33Z","updated_at":"2026-11-02T19:49:31.25882Z"}],"ghsa":[{"id":"GHSA-53v4-42fg-g287","title":"Apache ActiveMQ Deserialization of Untrusted Data vulnerability","description":"Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \n\nIn details, in ActiveMQ configurations, jetty allows org.jolokia.http.AgentServlet to handler request to /api/jolokia\n\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to create JmxRequest through JSONObject. And calls to org.jolokia.http.HttpRequestHandler#executeRequest.\n\nInto deeper calling stacks, org.jolokia.handler.ExecHandler#doHandleRequest is able to invoke through refection.\n\nAnd then, RCE is able to be achieved via jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\n\n1 Call newRecording.\n\n2 Call setConfiguration. And a webshell data hides in it.\n\n3 Call startRecording.\n\n4 Call copyTo method. The webshell will be written to a .jsp file.\n\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.","status":"published","published":"2023-11-28T18:30:23Z","modified":"2025-11-04T16:47:36Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-287","CWE-502"],"updated_at":"2026-11-02T14:39:06.376137Z"}],"nvd":[{"id":"CVE-2022-41678","description":"Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \n\nIn details, in ActiveMQ configurations, jetty allows\norg.jolokia.http.AgentServlet to handler request to /api/jolokia\n\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to\ncreate JmxRequest through JSONObject. And calls to\norg.jolokia.http.HttpRequestHandler#executeRequest.\n\nInto deeper calling stacks,\norg.jolokia.handler.ExecHandler#doHandleRequest can be invoked\nthrough refection. This could lead to RCE through via\nvarious mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\n\n1 Call newRecording.\n\n2 Call setConfiguration. And a webshell data hides in it.\n\n3 Call startRecording.\n\n4 Call copyTo method. The webshell will be written to a .jsp file.\n\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.\n","status":"published","published":"2023-11-28T16:15:06.84Z","modified":"2026-06-17T05:03:37.323Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T14:07:39.811118Z"}],"osv":[{"id":"GHSA-53v4-42fg-g287","title":"Apache ActiveMQ Deserialization of Untrusted Data vulnerability","description":"Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \n\nIn details, in ActiveMQ configurations, jetty allows org.jolokia.http.AgentServlet to handler request to /api/jolokia\n\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to create JmxRequest through JSONObject. And calls to org.jolokia.http.HttpRequestHandler#executeRequest.\n\nInto deeper calling stacks, org.jolokia.handler.ExecHandler#doHandleRequest is able to invoke through refection.\n\nAnd then, RCE is able to be achieved via jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\n\n1 Call newRecording.\n\n2 Call setConfiguration. And a webshell data hides in it.\n\n3 Call startRecording.\n\n4 Call copyTo method. The webshell will be written to a .jsp file.\n\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.","status":"published","published":"2023-11-28T18:30:23Z","modified":"2025-11-04T17:18:01.053166Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-287","CWE-502"],"updated_at":"2026-11-02T15:46:37.864461Z"},{"id":"OESA-2023-1925","title":"activemq security update","description":"The most popular and powerful open source messaging and Integration Patterns server.\r\n\r\nSecurity Fix(es):\r\n\r\nOnce an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \r\n\r\nIn details, in ActiveMQ configurations, jetty allows\norg.jolokia.http.AgentServlet to handler request to /api/jolokia\r\n\r\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to\ncreate JmxRequest through JSONObject. And calls to\norg.jolokia.http.HttpRequestHandler#executeRequest.\r\n\r\nInto deeper calling stacks,\norg.jolokia.handler.ExecHandler#doHandleRequest is able to invoke\nthrough refection.\r\n\r\nAnd then, RCE is able to be achieved via\njdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\r\n\r\n1 Call newRecording.\r\n\r\n2 Call setConfiguration. And a webshell data hides in it.\r\n\r\n3 Call startRecording.\r\n\r\n4 Call copyTo method. The webshell will be written to a .jsp file.\r\n\r\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.\n(CVE-2022-41678)","status":"published","published":"2023-12-15T11:06:22Z","modified":"2026-08-18T01:18:05.757786636Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:40.71472Z"},{"id":"UBUNTU-CVE-2022-41678","description":"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.","status":"published","published":"2023-11-28T16:15:00Z","modified":"2026-02-04T02:22:08.976611Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T16:53:55.502114Z"},{"id":"BIT-activemq-2022-41678","title":"Apache ActiveMQ: Insufficient API restrictions on Jolokia allow authenticated users to perform RCE","description":"Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \n\nIn details, in ActiveMQ configurations, jetty allows\norg.jolokia.http.AgentServlet to handler request to /api/jolokia\n\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to\ncreate JmxRequest through JSONObject. And calls to\norg.jolokia.http.HttpRequestHandler#executeRequest.\n\nInto deeper calling stacks,\norg.jolokia.handler.ExecHandler#doHandleRequest can be invoked\nthrough refection. This could lead to RCE through via\nvarious mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\n\n1 Call newRecording.\n\n2 Call setConfiguration. And a webshell data hides in it.\n\n3 Call startRecording.\n\n4 Call copyTo method. The webshell will be written to a .jsp file.\n\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.","status":"published","published":"2025-12-03T14:35:37.01Z","modified":"2026-09-08T08:45:10.186828108Z","updated_at":"2026-11-02T15:28:28.267217Z"},{"id":"CVE-2022-41678","title":"Apache ActiveMQ: Insufficient API restrictions on Jolokia allow authenticated users to perform RCE","description":"Once an user is authenticated on Jolokia, he can potentially trigger arbitrary code execution. \n\nIn details, in ActiveMQ configurations, jetty allows\norg.jolokia.http.AgentServlet to handler request to /api/jolokia\n\norg.jolokia.http.HttpRequestHandler#handlePostRequest is able to\ncreate JmxRequest through JSONObject. And calls to\norg.jolokia.http.HttpRequestHandler#executeRequest.\n\nInto deeper calling stacks,\norg.jolokia.handler.ExecHandler#doHandleRequest can be invoked\nthrough refection. This could lead to RCE through via\nvarious mbeans. One example is unrestricted deserialization in jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 11.\n\n1 Call newRecording.\n\n2 Call setConfiguration. And a webshell data hides in it.\n\n3 Call startRecording.\n\n4 Call copyTo method. The webshell will be written to a .jsp file.\n\nThe mitigation is to restrict (by default) the actions authorized on Jolokia, or disable Jolokia.\nA 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.\n","status":"published","published":"2023-11-28T15:08:38.338Z","modified":"2026-10-28T02:31:09.128844071Z","cwes":["CWE-287"],"updated_at":"2026-11-02T15:44:26.860704Z"},{"id":"DEBIAN-CVE-2022-41678","description":"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.","status":"published","published":"2023-11-28T16:15:06.84Z","modified":"2026-11-03T06:02:55.053036501Z","updated_at":"2026-11-03T06:43:19.563245Z"},{"id":"DLA-3936-1","title":"activemq - security update","status":"published","published":"2024-10-25T00:00:00Z","modified":"2026-03-09T01:18:03.450062Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"DSA-5798-1","title":"activemq - security update","status":"published","published":"2024-10-26T00:00:00Z","modified":"2026-03-09T02:09:58.548235Z","updated_at":"2026-11-02T15:46:17.892347Z"},{"id":"USN-6910-1","title":"activemq vulnerabilities","description":"Chess Hazlett discovered that Apache ActiveMQ incorrectly handled certain\ncommands. A remote attacker could possibly use this issue to terminate\nthe program, resulting in a denial of service. This issue only affected\nUbuntu 16.04 LTS. (CVE-2015-7559)\n\nPeter Stöckli discovered that Apache ActiveMQ incorrectly handled\nhostname verification. A remote attacker could possibly use this issue\nto perform a person-in-the-middle attack. This issue only affected Ubuntu\n16.04 LTS. (CVE-2018-11775)\n\nJonathan Gallimore and Colm Ó hÉigeartaigh discovered that Apache\nActiveMQ incorrectly handled authentication in certain functions.\nA remote attacker could possibly use this issue to perform a\nperson-in-the-middle attack. This issue only affected Ubuntu 16.04 LTS,\nUbuntu 18.04 LTS and Ubuntu 20.04 LTS. (CVE-2020-13920)\n\nGregor Tudan discovered that Apache ActiveMQ incorrectly handled\nLDAP authentication. A remote attacker could possibly use this issue\nto acquire unauthenticated access. This issue only affected Ubuntu 16.04\nLTS, Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. (CVE-2021-26117)\n\nIt was discovered that Apache ActiveMQ incorrectly handled\nauthentication. A remote attacker could possibly use this issue to run\narbitrary code. (CVE-2022-41678)\n\nIt was discovered that Apache ActiveMQ incorrectly handled\ndeserialization. A remote attacker could possibly use this issue to run\narbitrary shell commands. (CVE-2023-46604)\n","status":"published","published":"2024-07-23T20:39:26Z","modified":"2026-06-25T13:32:28.776549331Z","updated_at":"2026-11-02T16:58:17.914523Z"},{"id":"USN-7268-1","title":"activemq vulnerabilities","description":"It was discovered that Apache ActiveMQ incorrectly handled\nauthentication. A remote attacker could possibly use this issue to run\narbitrary code. (CVE-2022-41678)\n\nIt was discovered that Apache ActiveMQ incorrectly handled\ndeserialization. A remote attacker could possibly use this issue to run\narbitrary shell commands. (CVE-2023-46604)\n","status":"published","published":"2025-02-14T10:36:08Z","modified":"2026-02-10T04:46:30Z","updated_at":"2026-11-02T16:58:18.876384Z"}]}}