GitHub Advisoryadvisory · Maven

GHSA-gj5m-m88j-v7c3 Apache ActiveMQ's default configuration doesn't secure the API web context

HIGH Published 2024-05-02 Modified 2025-02-11 Official page ↗
Aliases
CVE-2024-32114
Ecosystem
Maven
Packages
org.apache.activemq:apache-activemq
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weaknesses
CWE-1188
Reviewed
2024-05-03

Affected packages

• Maven org.apache.activemq:apache-activemq: >= 6.0.0, < 6.1.2 → fixed in 6.1.2

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:     Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.

Related

Alias · CVE (1)

  • CVE-2024-32114 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… vulnerability

Weakness · CWE (1)

  • CWE-1188 Initialization of a Resource with an Insecure Default weakness

References