Skip to content
Fencer Vulns
medium 5.5

CVE-2020-10727 json

ActiveMQ Artemis has Insufficiently Protected Credentials

published 2020-06-26 6 y ago modified 2026-07-07 4 mo ago also GHSA-q9g8-9hpp-xc82 , EUVD-2022-4931

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.activemq:artemis-commons 2.13.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-10727 updated cvss 5.5

broker: resetUsers operation stores password in plain text

  • Red Hat AMQ
    fixed: vendor fix “When resetting a user an alternative is to use the broker instance CLI `/bin/artemis user reset` which is not affected by the flaw” RHSA-2020:2751

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.activemq:artemis-commons
>=2.7.0, <2.13.0
2.13.0

Affected products

  • Red Hat ActiveMQ Artemis

Classification

Weakness
  • CWE-312 Cleartext Storage of Sensitive Information
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.