GHSA-gj5m-m88j-v7c3

Suggest an improvement
Source
https://github.com/advisories/GHSA-gj5m-m88j-v7c3
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/05/GHSA-gj5m-m88j-v7c3/GHSA-gj5m-m88j-v7c3.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-gj5m-m88j-v7c3
Aliases
Published
2024-05-02T09:30:48Z
Modified
2024-05-04T08:11:42.112926Z
Severity
  • 8.5 (High) CVSS_V3 - CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H CVSS Calculator
Summary
Apache ActiveMQ's default configuration doesn't secure the API web context
Details

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.

Database specific
{
    "nvd_published_at": "2024-05-02T09:15:06Z",
    "cwe_ids": [
        "CWE-1188"
    ],
    "severity": "HIGH",
    "github_reviewed": true,
    "github_reviewed_at": "2024-05-03T17:47:07Z"
}
References

Affected packages

Maven / org.apache.activemq:apache-activemq

Package

Name
org.apache.activemq:apache-activemq
View open source insights on deps.dev
Purl
pkg:maven/org.apache.activemq/apache-activemq

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.0.0
Fixed
6.1.2

Affected versions

6.*

6.0.0
6.0.1
6.1.0
6.1.1