CVE-2024-32114 – org.apache.activemq:apache-activemq

Package

Manager: maven
Name: org.apache.activemq:apache-activemq
Vulnerable Version: >=6.0.0 <6.1.2

Severity

Level: High

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

EPSS: 0.01563 pctl0.80798

Details

Apache ActiveMQ's default configuration doesn't secure the API web context 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.

Metadata

Created: 2024-05-02T09:30:48Z
Modified: 2025-02-11T19:03:08Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/05/GHSA-gj5m-m88j-v7c3/GHSA-gj5m-m88j-v7c3.json
CWE IDs: ["CWE-1188"]
Alternative ID: GHSA-gj5m-m88j-v7c3
Finding: F164
Auto approve: 1