CVE-2022-23913

Apache ActiveMQ Artemis before version 2.29.0 allows access to diagnostic information and controls through MBeans, including the Log4J2 MBean, which is not meant for exposure to non-administrative users. This could allow an authenticated attacker to write arbitrary files to the filesystem and indirectly achieve RCE.

The getObject method of the javax.jms.ObjectMessage class in Apache ActiveMQ Artemis before version 1.4.0 may allow remote authenticated users with permission to send messages to the Artemis broker to deserialize arbitrary objects and execute arbitrary code.

The vulnerability in Apache ActiveMQ Artemis involves the insertion of sensitive information into the log file. All broker property values are logged when the org.apache.activemq.artemis.core.config.impl.ConfigurationImpl logger has debug level enabled.

A vulnerability exists in Apache ActiveMQ Artemis that allows a user with permissions to create queues to modify the routing type of an address, even if they do not have permission to create that address. This could lead to sending messages with a routing type not supported by the address.

In Apache ActiveMQ Artemis prior to version 2.24.0, an attacker could show malicious content and/or redirect users to a malicious URL in the web console by using HTML in the name of an address or queue.

In the OpenWire protocol of Apache ActiveMQ Artemis 2.15.0, a vulnerability was found that allowed bypassing policy-based access control when creating advisory messages for the entire session. The production of these messages was not subject to access control in error.

In Apache ActiveMQ Artemis versions 2.5.0 to 2.13.0, there is an XSS vulnerability that can be exploited through a specially crafted MQTT packet containing an XSS payload in the client-id or topic name. The XSS payload is injected into the admin console's browser.