# CVE-2023-50780: Apache ActiveMQ Artemis: Authenticated users could perform RCE via Jolokia MBeans

> Authenticated attackers can achieve remote code execution by accessing exposed Log4J2 MBeans via the Jolokia endpoint in Apache ActiveMQ Artemis.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2024
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-443j-grxv-2pgv

## What is CVE-2023-50780?

CVE-2023-50780 is a high-severity missing authorization vulnerability in Apache ActiveMQ Artemis, published on 14 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2023-50780?

2 open source packages ship an affected version, including org.apache.activemq:artemis-cli. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.activemq:artemis-cli` | Maven | All versions | 2.29.0 |
| `org.apache.activemq:artemis-cli` | Maven | All versions | 2.29.0 |

Products: Apache Artemis.

## How do I fix CVE-2023-50780?

Upgrade org.apache.activemq:artemis-cli to 2.29.0 or later.

## Is CVE-2023-50780 being exploited?

There is no known exploitation of CVE-2023-50780 in the wild and no public exploit code.

Public exploit code:

- CVE-2023-50780: Dangerous MBeans Accessible via Jolokia API in Apache ActiveMQ Artemis (github_poc): https://github.com/mbadanoiu/CVE-2023-50780

## Other vulnerabilities in Apache ActiveMQ Artemis

- [CVE-2026-57967](https://insights.sbomify.com/CVE-2026-57967/): Apache Artemis, Apache ActiveMQ Artemis: Missing authentication on CORE protocol session reattachment (critical 9.8)
- [CVE-2026-27446](https://insights.sbomify.com/CVE-2026-27446/): Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation (critical 9.3)
- [CVE-2026-49364](https://insights.sbomify.com/CVE-2026-49364/): Information disclosure in Apache ActiveMQ Artemis (critical 9.1)
- [CVE-2026-67593](https://insights.sbomify.com/CVE-2026-67593/): Missing authorization in Apache ActiveMQ Artemis (critical 9.1)
- [CVE-2026-49362](https://insights.sbomify.com/CVE-2026-49362/): Missing authorization in Apache ActiveMQ Artemis (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50780 and fix it if it is affected.

What it is: CVE-2023-50780 is a high-severity missing authorization vulnerability in Apache ActiveMQ Artemis, published on 14 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50780 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.activemq:artemis-cli (Maven): affected all versions; fixed in 2.29.0
- org.apache.activemq:artemis-cli (Maven): affected all versions; fixed in 2.29.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-50780/ (Markdown: https://insights.sbomify.com/CVE-2023-50780/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-50780
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-50780
- OSV: https://osv.dev/vulnerability/CVE-2023-50780

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-50780/
Summaries are generated and may contain mistakes; the official description above is the record.