CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 3CVE-2025-27533 – Apache ActiveMQ: Unchecked buffer length can cause excessive memory allocation
https://notcve.org/view.php?id=CVE-2025-27533
07 May 2025 — Memory Allocation with Excessive Size Value vulnerability in Apache ActiveMQ. During unmarshalling of OpenWire commands the size value of buffers was not properly validated which could lead to excessive memory allocation and be exploited to cause a denial of service (DoS) by depleting process memory, thereby affecting applications and services that rely on the availability of the ActiveMQ broker when not using mutual TLS connections. This issue affects Apache ActiveMQ: from 6.0.0 before 6.1.6, from 5.18.0 b... • https://packetstorm.news/files/id/191182 • CWE-789: Memory Allocation with Excessive Size Value •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0CVE-2025-29953 – Apache ActiveMQ NMS OpenWire Client: deserialization allowlist bypass
https://notcve.org/view.php?id=CVE-2025-29953
18 Apr 2025 — Deserialization of Untrusted Data vulnerability in Apache ActiveMQ NMS OpenWire Client. This issue affects Apache ActiveMQ NMS OpenWire Client before 2.1.1 when performing connections to untrusted servers. Such servers could abuse the unbounded deserialization in the client to provide malicious responses that may eventually cause arbitrary code execution on the client. Version 2.1.0 introduced a allow/denylist feature to restrict deserialization, but this feature could be bypassed. The .NET team has depreca... • https://lists.apache.org/thread/vc1sj9y3056d3kkhcvrs9fyw5w8kpmlx • CWE-502: Deserialization of Untrusted Data •
CVSS: 6.8EPSS: 0%CPEs: 1EXPL: 0CVE-2025-27391 – Apache ActiveMQ Artemis: Passwords leaking from broker properties in the debug log
https://notcve.org/view.php?id=CVE-2025-27391
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: 0CVE-2025-27427 – Apache ActiveMQ Artemis: Address routing-type can be updated by user without the createAddress permission
https://notcve.org/view.php?id=CVE-2025-27427
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: 1CVE-2023-50780 – Apache ActiveMQ Artemis: Authenticated users could perform RCE via Jolokia MBeans
https://notcve.org/view.php?id=CVE-2023-50780
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: 0CVE-2024-32114 – Apache ActiveMQ: Jolokia and REST API were not secured with default configuration
https://notcve.org/view.php?id=CVE-2024-32114
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 •