Bug 1827200 (CVE-2020-10727) - CVE-2020-10727 broker: resetUsers operation stores password in plain text
Summary: CVE-2020-10727 broker: resetUsers operation stores password in plain text
Alias: CVE-2020-10727
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On:
Blocks: 1827209 1827776
TreeView+ depends on / blocked
Reported: 2020-04-23 12:22 UTC by Michael Kaplan
Modified: 2020-06-25 17:20 UTC (History)
7 users (show)

Fixed In Version: ActiveMQ Artemis 2.12.0
Doc Type: If docs needed, set a value
Doc Text:
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.
Clone Of:
Last Closed: 2020-06-25 17:20:33 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:2751 None None None 2020-06-25 14:14:58 UTC

Description Michael Kaplan 2020-04-23 12:22:53 UTC
If you execute the resetUsers operation, the new password is stored in plain text in the etc/artemis-users.properties file.

Comment 1 Michael Kaplan 2020-04-23 12:22:57 UTC
External References:


Comment 2 Michael Kaplan 2020-04-23 12:24:51 UTC

Name: Justin Bertram (Reporter)

Comment 6 Jonathan Christison 2020-04-29 10:48:11 UTC

When resetting a user an alternative is to use the broker instance CLI `/bin/artemis user reset` which is not affected by the flaw

Comment 10 errata-xmlrpc 2020-06-25 14:14:56 UTC
This issue has been addressed in the following products:

  Red Hat AMQ

Via RHSA-2020:2751 https://access.redhat.com/errata/RHSA-2020:2751

Comment 11 Product Security DevOps Team 2020-06-25 17:20:33 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.