Aller au contenu
en Se connecter
8.5 Élevée

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…

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: <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.

Produits et versions touchés

Produit Versions touchées Corrigé en
Apache ActiveMQ 6.0 6.0.0 → 6.1.1 Pas de correctif indiqué
ActiveMQ 6.x Pas de correctif indiqué

Références

Chronologie

  1. Publiée
  2. Dernière modification

Autres CVE de Apache ActiveMQ

Les 40 CVE de Apache ActiveMQ →
CVE-2026-108500 Apache ActiveMQ: LDAPAuthorizationMap allows authorization bypass via DN injection Non notée CVE-2026-108946 Apache ActiveMQ, ActiveMQ Broker: The broker does not verify user provided connection id matches connection Non notée CVE-2026-111822 Apache ActiveMQ, Apache ActiveMQ Runtime Config: ActiveMQ retains write access after live ACL revocation Non notée CVE-2026-111821 Apache ActiveMQ, Apache ActiveMQ KahaDB: Oversized client identifier strings poison the KahaDB journal Non notée
Suivre cette CVE