dbcve.org
ArtemisApplication · Apache

CVE-2020-13932

MEDIUM · 6.1 CVSS v3.1 Published 2020-07-20
Fix available
A fix is available. Upgrade to after 2.13.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
In Apache ActiveMQ Artemis 2.5.0 to 2.13.0, a specially crafted MQTT packet which has an XSS payload as client-id or topic name can exploit this vulnerability. The XSS payload is being injected into the admin console's browser. The XSS payload is triggered in the diagram plugin; queue node and the info section.

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

A stored XSS vulnerability in Apache ActiveMQ Artemis 2.5.0-2.13.0 allows attackers to inject malicious JavaScript via MQTT client-id or topic name fields. This unsanitized input is rendered in the admin console's diagram plugin, queue node, and info section, executing the payload in the browser of any admin user viewing these elements.

MitigationUpgrade to Apache ActiveMQ Artemis version 2.13.1 or later. If immediate patching is not feasible, restrict or disable access to the admin console to trusted users only to reduce exposure.

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.5.0, <= 2.13.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installation
    Locate the Artemis installation directory and check for the artemis-core.jar or artemis-distribution binary. On Linux, common paths include /opt/apache-artemis, /usr/share/activemq-artemis, or the user's home directory. Run 'find / -name "artemis" -type f 2>/dev/null' to locate binaries.
    Affected if Artemis is present on the system
  2. Determine installed Artemis version
    Check the version file or pom.xml in the installation directory. You can also run 'artemis --version' from the bin directory, or inspect the lib/artemis-core-*.jar filename which contains the version number.
    Affected if Version is 2.5.0, 2.6.0, 2.7.0, 2.8.0, 2.9.0, 2.10.0, 2.11.0, 2.12.0, 2.13.0, or any version between 2.5.0 and 2.13.0 inclusive
  3. Verify admin console is accessible
    Check if the web server is running on the configured port (default 8161). Look in etc/bootstrap.xml or etc/activemq-artemis.xml for web server configuration. Attempt to access http://localhost:8161/console or check netstat for listening ports in the 8160-8170 range.
    Affected if Admin console port is open and reachable from user-accessible network
  4. Confirm MQTT protocol is enabled
    Inspect etc/broker.xml or etc/activemq-artemis.xml for <connector name="mqtt"> entries. Check etc/acceptors.xml for an acceptor configured with protocol=mqtt. Look for port 1883 (default MQTT) in netstat output.
    Affected if MQTT acceptor or connector is configured and active
  5. Inspect MQTT client identifiers and topic names
    If you have access to the broker management interface or logs, review recently connected MQTT client IDs and created topic names. Check queue Names and addresses in the Artemis address settings for any suspicious patterns containing script tags or javascript: strings.
    Affected if MQTT client-id or topic name fields contain unsanitized user input that could include XSS payloads

You are affected if Apache ActiveMQ Artemis versions 2.5.0 through 2.13.0 are installed, the admin console is accessible, and MQTT protocol is enabled with potential unsanitized client identifiers or topic names present.

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.

From vendor data
Upgrade available Upgrade to a release after 2.13.0
Interim mitigation

Upgrade to Apache ActiveMQ Artemis version 2.13.1 or later. If immediate patching is not feasible, restrict or disable access to the admin console to trusted users only to reduce exposure.

Fix this in Artemis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13932 — 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-2020-13932 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