dbcve.org
ArtemisApplication · Apache

CVE-2023-50780

HIGH · 8.8 CVSS v3.1 Published 2024-10-14
Fix available
A fix is available. Upgrade to 2.29.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache ActiveMQ Artemis versions before 2.29.0 exposed the Log4J2 MBean through the authenticated Jolokia endpoint, allowing authenticated attackers to write arbitrary files to the filesystem and achieve remote code execution.

MitigationUpgrade to Apache ActiveMQ Artemis version 2.29.0 or later, which removes exposure of the Log4J2 MBean to non-administrative users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ArtemisApplication
Affected:< 2.29.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache ActiveMQ Artemis version
    Locate the Artemis installation and check the version file or bootstrap configuration. Common locations include the 'artemis' or 'artemis-version.txt' file in the installation directory, or check the bootstrap.xml configuration for version information.
    Affected if The installed version is any version before 2.29.0 (e.g., 2.28.0, 2.27.0, earlier).
  2. Determine if Jolokia endpoint is enabled
    Inspect the broker configuration (typically broker.xml or bootstrap.xml) for Jolokia plugin configuration. Look for < JolokiaAgent > or similar Jolokia-related XML elements that enable the Jolokia REST API endpoint.
    Affected if Jolokia endpoint is enabled and configured in the broker.
  3. Verify accessibility of Jolokia to non-administrative users
    Review user role definitions in the broker security configuration (often in login.config or within broker.xml) to determine if any authenticated users exist with roles other than 'admin' or 'administrator' that can access the Jolokia endpoint.
    Affected if Non-administrative authenticated users exist who can access the Jolokia endpoint.

You are affected if you are running Apache ActiveMQ Artemis version 2.29.0 or later - the vulnerability only applies to versions before 2.29.0 that have the Jolokia endpoint enabled and accessible to authenticated (non-admin) users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.29.0 or later
Fixed in 2.29.0
Interim mitigation

Upgrade to Apache ActiveMQ Artemis version 2.29.0 or later, which removes exposure of the Log4J2 MBean to non-administrative users.

Recommended fix High confidence

Apache ActiveMQ Artemis 2.29.0 or later

  1. 1. Backup your current Apache ActiveMQ Artemis installation including configuration files and data directories
  2. 2. Download Apache ActiveMQ Artemis version 2.29.0 or later from the official Apache distribution repository (https://activemq.apache.org/artemis/download)
  3. 3. Stop the currently running Artemis broker instance
  4. 4. Install the new version (2.29.0+) using your preferred method (zip extraction or package manager)
  5. 5. Restore your configuration from the backup, ensuring any custom configurations are preserved
  6. 6. Start the Artemis broker with the upgraded version
  7. 7. Verify that the Log4J2 MBean is no longer exposed through the Jolokia endpoint by checking the MBean inventory or testing with a non-admin user

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Artemis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50780 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data