Apache ActiveMQ's default configuration doesn't secure the API web context

高 8.8CVE-2024-32114 · BIT-activemq-2024-32114 · GHSA-gj5m-m88j-v7c3 · 02/05/2024 公開 · 17/06/2026 更新

要点

CVE-2024-32114 は org.apache.activemq:apache-activemq, activemq (apache) に影響する深刻度「高」 (CVSS 8.8) の脆弱性です。
今後30日間に悪用される確率（EPSS）：7.1%（全脆弱性の 94.3% より高い）。
対処：6.1.2 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
org.apache.activemq:apache-activemq Maven	`≥ 6.0.0, < 6.1.2`	`6.1.2`
activemq apache	`≥ 6.0.0, < 6.1.2`	`6.1.2`

概要

To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping"> <property name="constraint" ref="securityConstraint" /> <property name="pathSpec" value="/" /> </bean>

Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.

NVD の説明

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: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping"> <property name="constraint" ref="securityConstraint" /> <property name="pathSpec" value="/" /> </bean> Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.