https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 00:14:20 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-03523 bdu:2024-03523 https://cve.radiocsirt.org/vuln/bdu:2024-03523 https://cve.radiocsirt.org/vuln/cnvd-2024-27491 cnvd-2024-27491 https://cve.radiocsirt.org/vuln/cnvd-2024-27491 https://cve.radiocsirt.org/vuln/euvd-2026-5095 EUVD-2026-5095 https://cve.radiocsirt.org/vuln/euvd-2026-5095 https://cve.radiocsirt.org/vuln/fkie_cve-2024-32114 <p>In Apache ActiveMQ 6.x, the default configuration doesn&#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).</p> <p>To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: &lt;bean id=&#34;securityConstraintMapping&#34; class=&#34;org.eclipse.jetty.security.ConstraintMapping&#34;&gt;   &lt;property name=&#34;constraint&#34; ref=&#34;securityConstraint&#34; /&gt;   &lt;property name=&#34;pathSpec&#34; value=&#34;/&#34; /&gt; &lt;/bean&gt;</p> <p>Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.</p> <p>In Apache ActiveMQ 6.x, the default configuration doesn&#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).</p> <p>To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: &lt;bean id=&#34;securityConstraintMapping&#34; class=&#34;org.eclipse.jetty.security.ConstraintMapping&#34;&gt;   &lt;property name=&#34;constraint&#34; ref=&#34;securityConstraint&#34; /&gt;   &lt;property name=&#34;pathSpec&#34; value=&#34;/&#34; /&gt; &lt;/bean&gt;</p> <p>Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-32114 https://cve.radiocsirt.org/vuln/ghsa-gj5m-m88j-v7c3 <p><strong>Affected:</strong> Maven: org.apache.activemq:apache-activemq</p> <p>In Apache ActiveMQ 6.x, the default configuration doesn&#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).</p> <p>To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: &lt;bean id=&#34;securityConstraintMapping&#34; class=&#34;org.eclipse.jetty.security.ConstraintMapping&#34;&gt;   &lt;property name=&#34;constraint&#34; ref=&#34;securityConstraint&#34; /&gt;   &lt;property name=&#34;pathSpec&#34; value=&#34;/&#34; /&gt; &lt;/bean&gt;</p> <p>Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.</p> <p><strong>Affected:</strong> Maven: org.apache.activemq:apache-activemq</p> <p>In Apache ActiveMQ 6.x, the default configuration doesn&#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).</p> <p>To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: &lt;bean id=&#34;securityConstraintMapping&#34; class=&#34;org.eclipse.jetty.security.ConstraintMapping&#34;&gt;   &lt;property name=&#34;constraint&#34; ref=&#34;securityConstraint&#34; /&gt;   &lt;property name=&#34;pathSpec&#34; value=&#34;/&#34; /&gt; &lt;/bean&gt;</p> <p>Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.</p> https://cve.radiocsirt.org/vuln/ghsa-gj5m-m88j-v7c3 https://cve.radiocsirt.org/vuln/gsd-2024-32114 gsd-2024-32114 https://cve.radiocsirt.org/vuln/gsd-2024-32114 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1010 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache ActiveMQ ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache ActiveMQ ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1010