First published: Mon Oct 14 2024(Updated: )
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.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.activemq:artemis-cli | <2.29.0 | 2.29.0 |
Apache ActiveMQ Artemis | <2.29.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-50780 has been classified as a medium severity vulnerability due to the exposure of sensitive diagnostic information.
To mitigate CVE-2023-50780, upgrade Apache ActiveMQ Artemis to version 2.29.0 or later.
CVE-2023-50780 affects Apache ActiveMQ Artemis versions prior to 2.29.0.
The main issue with CVE-2023-50780 is the exposure of the Log4J2 MBean through the Jolokia endpoint, which should not be accessible to non-administrative users.
No, in versions prior to 2.29.0, user access to MBeans was not adequately restricted, allowing unauthorized access to diagnostic controls.