Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-13932 medium CVSS 6.1

Cross-Site Scripting (XSS) in org.apache.activemq:apache-artemis (CVE-2020-13932)

Summary

Cross-site scripting in org.apache.activemq:apache-artemis (CVE-2020-13932). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.14.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-13932 has been found in org.apache.activemq:apache-artemis.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade org.apache.activemq:apache-artemis to 2.14.0 or later.
If unsure, ask your IT team or search "org.apache.activemq:apache-artemis CVE-2020-13932" on the vendor's site.

CVE-2020-13932 (org.apache.activemq:apache-artemis) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.14.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in org.apache.activemq:apache-artemis.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.activemq:apache-artemis.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.14.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.activemq:apache-artemis を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.activemq:apache-artemis to 2.14.0

    ステージング環境で 2.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.activemq:apache-artemis
[{"type":"ECOSYSTEM","events":[{"introduced":"2.5.0"},{"fixed":"2.14.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details