4 results (0.005 seconds)

CVSS: 6.8EPSS: %CPEs: 1EXPL: 0

09 Apr 2025 — Insertion of Sensitive Information into Log File vulnerability in Apache ActiveMQ Artemis. All the values of the broker properties are logged when the org.apache.activemq.artemis.core.config.impl.ConfigurationImpl logger has the debug level enabled. This issue affects Apache ActiveMQ Artemis: from 1.5.1 before 2.40.0. It can be mitigated by restricting log access to only trusted users. Users are recommended to upgrade to version 2.40.0, which fixes the issue. • https://lists.apache.org/thread/25p96cvzl1mkt29lwm2d8knklkoqolps • CWE-532: Insertion of Sensitive Information into Log File •

CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0

01 Apr 2025 — A vulnerability exists in Apache ActiveMQ Artemis whereby a user with the createDurableQueue or createNonDurableQueue permission on an address can augment the routing-type supported by that address even if said user doesn't have the createAddress permission for that particular address. When combined with the send permission and automatic queue creation a user could successfully send a message with a routing-type not supported by the address when that message should actually be rejected on the basis that the... • https://lists.apache.org/thread/8dzlm2vkqphyrnkrby8r8kzndsm5o6x8 • CWE-863: Incorrect Authorization •

CVSS: 9.0EPSS: 0%CPEs: 1EXPL: 1

14 Oct 2024 — Apache ActiveMQ Artemis allows access to diagnostic information and controls through MBeans, which are also exposed through the authenticated Jolokia endpoint. Before version 2.29.0, this also included the Log4J2 MBean. This MBean is not meant for exposure to non-administrative users. This could eventually allow an authenticated attacker to write arbitrary files to the filesystem and indirectly achieve RCE. Users are recommended to upgrade to version 2.29.0 or later, which fixes the issue. • https://github.com/mbadanoiu/CVE-2023-50780 • CWE-285: Improper Authorization •

CVSS: 8.5EPSS: 1%CPEs: 1EXPL: 0

02 May 2024 — 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 requiremen... • https://activemq.apache.org/security-advisories.data/CVE-2024-32114-announcement.txt • CWE-1188: Initialization of a Resource with an Insecure Default •