Create 20240503001-Apache-ActiveMQ-Vulnerability.md (#698)

* Create 20240503001-Apache-ActiveMQ-Vulnerability.md new * Format markdown docs --------- Co-authored-by: jasonkasih <[email protected]>
wagov · May 3, 2024 · ef3392a · ef3392a
1 parent 6ece316
commit ef3392a
Showing 1 changed file with 38 additions and 0 deletions.
diff --git a/docs/advisories/20240503001-Apache-ActiveMQ-Vulnerability.md b/docs/advisories/20240503001-Apache-ActiveMQ-Vulnerability.md
@@ -0,0 +1,38 @@
+# Apache ActiveMQ Vulnerability - 20240503001
+
+## Overview
+
+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:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<bean class="org.eclipse.jetty.security.ConstraintMapping" id="securityConstraintMapping">
+ <property name="constraint" ref="securityConstraint"/>
+ <property name="pathSpec" value="/"/>
+</bean>
+
+```
+
+Or Apache encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
+
+## What is vulnerable?
+
+| CVE                                                               | Severity | CVSS | Product(s) Affected              | Dated       |
+| ----------------------------------------------------------------- | -------- | ---- | -------------------------------- | ----------- |
+| [CVE-2024-32114](https://nvd.nist.gov/vuln/detail/CVE-2024-32114) | High     | 8.5  | Apache ActiveMQ 6.x before 6.1.2 | 02-May-2024 |
+
+## What has been observed?
+
+There is no evidence of exploitation affecting Western Australian Government networks at the time of publishing.
+
+## Recommendation
+
+The WA SOC recommends administrators apply the solutions as per vendor instructions to all affected devices within expected timeframe of *one month...* (refer [Patch Management](../guidelines/patch-management.md)):
+
+- [Stable Channel Update for Desktop - Apache](https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt)
+
+## Additional References
+
+- [CVE-2024-32114: High-Severity Vulnerability Exposed in Apache ActiveMQ](https://securityonline.info/cve-2024-32114-high-severity-vulnerability-exposed-in-apache-activemq/)