<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 22:57:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-32114 — Apache ActiveMQ: Jolokia and REST API were not secured with default configuration</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-32114</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache ActiveMQ, apache activemq&lt;/p&gt;
&lt;p&gt;In Apache ActiveMQ 6.x, the default configuration doesn&amp;#39;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).&lt;/p&gt;
&lt;p&gt;To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:
&amp;lt;bean id=&amp;#34;securityConstraintMapping&amp;#34; class=&amp;#34;org.eclipse.jetty.security.ConstraintMapping&amp;#34;&amp;gt;
  &amp;lt;property name=&amp;#34;constraint&amp;#34; ref=&amp;#34;securityConstraint&amp;#34; /&amp;gt;
  &amp;lt;property name=&amp;#34;pathSpec&amp;#34; value=&amp;#34;/&amp;#34; /&amp;gt;
&amp;lt;/bean&amp;gt;&lt;/p&gt;
&lt;p&gt;Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache ActiveMQ, apache activemq&lt;/p&gt;
&lt;p&gt;In Apache ActiveMQ 6.x, the default configuration doesn&amp;#39;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).&lt;/p&gt;
&lt;p&gt;To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement:
&amp;lt;bean id=&amp;#34;securityConstraintMapping&amp;#34; class=&amp;#34;org.eclipse.jetty.security.ConstraintMapping&amp;#34;&amp;gt;
  &amp;lt;property name=&amp;#34;constraint&amp;#34; ref=&amp;#34;securityConstraint&amp;#34; /&amp;gt;
  &amp;lt;property name=&amp;#34;pathSpec&amp;#34; value=&amp;#34;/&amp;#34; /&amp;gt;
&amp;lt;/bean&amp;gt;&lt;/p&gt;
&lt;p&gt;Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-32114</guid>
    </item>
  </channel>
</rss>
