{"id":"CVE-2024-32114","aliases":["BIT-activemq-2024-32114","EUVD-2024-1626","GHSA-gj5m-m88j-v7c3"],"status":"published","title":"Apache ActiveMQ: Jolokia and REST API were not secured with default configuration","description":"In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).\nIt means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).\n\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\n\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e\n  \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e\n  \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\n\u003c/bean\u003e\n\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.","severity":{"version":"3.1","score":8.5,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.07148,"percentile":0.94353,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-1188"],"published":"2024-05-02T08:29:18Z","modified":"2026-10-28T02:30:42Z","exploits":[{"source":"nuclei","id":"CVE-2024-32114","title":"Apache ActiveMQ 6.x \u003c 6.1.2 - Broken Access Control","type":"detection template","url":"https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2024/CVE-2024-32114.yaml"},{"source":"pocgithub","id":"Catherines77/ActiveMQ-EXPtools","title":"Catherines77/ActiveMQ-EXPtools","date":"2026-04-20","url":"https://github.com/Catherines77/ActiveMQ-EXPtools"}],"fixes":[{"ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","fixed_in":["6.1.2"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"activemq","fixed_in":["6.1.2"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.2"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"activemq","ranges":[{"type":"SEMVER","events":[{"introduced":"6.0.0"},{"fixed":"6.1.2"}]}]},{"source":"osv","ecosystem":"Maven","package":"org.apache.activemq:apache-activemq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.2"}]}],"versions":["6.0.0","6.0.1","6.1.0","6.1.1"]}],"products":[{"vendor":"apache","product":"activemq"},{"vendor":"apache software foundation","product":"apache activemq"}],"references":[{"url":"https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt","tags":["vendor-advisory","x_transferred","Vendor Advisory","web","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-32114","tags":["advisory"]},{"url":"https://github.com/apache/activemq/pull/1201","tags":["web"]},{"url":"https://github.com/apache/activemq/commit/43cc596219b6a8c8b5a54fbda3fb68cb4424f2d0","tags":["web"]},{"url":"https://issues.apache.org/jira/browse/AMQ-9477","tags":["web"]},{"url":"https://github.com/advisories/GHSA-gj5m-m88j-v7c3"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/32xxx/CVE-2024-32114.json","tags":["advisory"]},{"url":"https://github.com/apache/activemq","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2024-32114","title":"Apache ActiveMQ: Jolokia and REST API were not secured with default configuration","description":"In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).\nIt means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).\n\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\n\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e\n  \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e\n  \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\n\u003c/bean\u003e\n\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.\n","status":"published","published":"2024-05-02T08:29:18.219Z","modified":"2024-08-02T02:06:44.047Z","cvss":[{"version":"3.1","score":8.5,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T14:34:15.662528Z"}],"euvd":[{"id":"EUVD-2024-1626","description":"In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).\nIt means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).\n\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\n\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e\n  \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e\n  \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\n\u003c/bean\u003e\n\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.\n","status":"published","published":"2024-05-02T08:29:18Z","modified":"2024-08-02T02:06:44Z","cvss":[{"version":"3.1","score":8.5,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-03T03:50:23.537508Z"}],"ghsa":[{"id":"GHSA-gj5m-m88j-v7c3","title":"Apache ActiveMQ's default configuration doesn't secure the API web context","description":"In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).\n\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\n\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e\n  \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e\n  \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\n\u003c/bean\u003e\n\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.","status":"published","published":"2024-05-02T09:30:48Z","modified":"2025-02-11T19:03:09Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T14:38:30.754382Z"}],"nvd":[{"id":"CVE-2024-32114","description":"In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).\nIt means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).\n\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\n\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e\n  \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e\n  \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\n\u003c/bean\u003e\n\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.\n","status":"published","published":"2024-05-02T09:15:06.99Z","modified":"2026-06-17T07:29:18.4Z","cvss":[{"version":"3.1","score":8.5,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H","level":"high","assessor":"secondary"},{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T14:09:56.122111Z"}],"osv":[{"id":"CVE-2024-32114","title":"Apache ActiveMQ: Jolokia and REST API were not secured with default configuration","description":"In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).\nIt means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).\n\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\n\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e\n  \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e\n  \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\n\u003c/bean\u003e\n\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.\n","status":"published","published":"2024-05-02T08:29:18.219Z","modified":"2026-10-28T02:30:42.422459165Z","cvss":[{"version":"3.1","score":8.5,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H","level":"high"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T15:44:40.391953Z"},{"id":"GHSA-gj5m-m88j-v7c3","title":"Apache ActiveMQ's default configuration doesn't secure the API web context","description":"In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).\n\nTo mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\n\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e\n  \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e\n  \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\n\u003c/bean\u003e\n\nOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.","status":"published","published":"2024-05-02T09:30:48Z","modified":"2025-02-11T19:25:04.056288Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T15:46:47.822182Z"},{"id":"BIT-activemq-2024-32114","description":"In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located).It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API).To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:\u003cbean id=\"securityConstraintMapping\" class=\"org.eclipse.jetty.security.ConstraintMapping\"\u003e  \u003cproperty name=\"constraint\" ref=\"securityConstraint\" /\u003e  \u003cproperty name=\"pathSpec\" value=\"/\" /\u003e\u003c/bean\u003eOr we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.","status":"published","published":"2024-05-04T07:16:13.914Z","modified":"2024-05-04T08:11:42.112926Z","updated_at":"2026-11-02T15:28:28.267217Z"}]}}