A flaw was found in Red Hats AMQ Broker, which stores certain passwords in a secret security-properties-prop-module, defined in ActivemqArtemisSecurity CR; however, they are shown in plaintext in the StatefulSet details yaml of AMQ Broker.
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jboss_a-mq | Redhat | 7 (including) | 7 (including) |
| Jboss_middleware | Redhat | 1 (including) | 1 (including) |
| RHEL-8 based Middleware Containers | RedHat | amq7/amq-broker-rhel8-operator:7.11.1-9 | * |
| RHEL-8 based Middleware Containers | RedHat | amq7/amq-broker-rhel8-operator-bundle:7.11.1-12 | * |
Because the information is stored in cleartext (i.e., unencrypted), attackers could potentially read it. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information. When organizations adopt cloud services, it can be easier for attackers to access the data from anywhere on the Internet. In some systems/environments such as cloud, the use of “double encryption” (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.