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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2024-32114)

The version of Apache ActiveMQ running on the remote host is 6.x prior to 6.1.2. It is, therefore, affected by an insecure the API web that a attacker can use without any required authentication.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
415164	SCA: security update for org.apache.activemq:apache-activemq (GHSA-gj5m-m88j-v7c3)	Tenable Cloud Security	SCA Checks	Local	high
415164	SCA: security update for org.apache.activemq:apache-activemq (GHSA-gj5m-m88j-v7c3)	Tenable Self-Hosted Container Security	SCA Checks	Local	high
194951	Apache ActiveMQ 6.x < 6.1.2 Insecure Web API Vulnerability	Nessus	CGI abuses	Combined	high

Detections

Analytics

CVE-2024-32114

high

Tenable Plugins

high

high

high