Categories
CVE-2020-10727 medium CVSS 5.5

Vulnerability in org.apache.activemq:artemis-commons (CVE-2020-10727)

Summary

Vulnerability in org.apache.activemq:artemis-commons (CVE-2020-10727). Confidential information can be exposed externally. Exploitable via resetUsers. Mitigation: upgrade to 2.13.0 or later.

Original description

The description as published by the source.

A flaw was found in ActiveMQ Artemis management API from version 2.7.0 up until 2.12.0, where a user inadvertently stores passwords in plaintext in the Artemis shadow file (etc/artemis-users.properties file) when executing the resetUsers operation. A local attacker can use this flaw to read the contents of the Artemis shadow file.

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-10727 has been found in org.apache.activemq:artemis-commons.
Attackers can target a specific entry point like resetUsers over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade org.apache.activemq:artemis-commons to 2.13.0 or later.
If unsure, ask your IT team or search "org.apache.activemq:artemis-commons CVE-2020-10727" on the vendor's site.

CVE-2020-10727 (org.apache.activemq:artemis-commons) — CWE-312 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: resetUsers
Patched: 2.13.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

A vulnerability (CWE-312) exists in org.apache.activemq:artemis-commons. Attackers reach the vulnerable code path via resetUsers.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.activemq:artemis-commons. Attack surface: resetUsers.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.13.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:artemis-commons を使っているサービスとバージョンを洗い出す。

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

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

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

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

Affected packages

maven org.apache.activemq:artemis-commons
[{"type":"ECOSYSTEM","events":[{"introduced":"2.7.0"},{"fixed":"2.13.0"}]}]

References

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