A flaw was found in noobaa-operator in versions before 5.7.0, where internal RPC AuthTokens between the noobaa operator and the noobaa core are leaked into log files. An attacker with access to the log files could use this AuthToken to gain additional access into noobaa deployment and can read/modify system configuration.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Noobaa-operator | Redhat | * | 5.7.0 (excluding) |
| Red Hat OpenShift Container Storage 4.6.0 on RHEL-8 | RedHat | ocs4/mcg-rhel8-operator:5.6.0-57.43b2f28.5.6 | * |
| Red Hat OpenShift Container Storage 4.7.0 on RHEL-8 | RedHat | ocs4/mcg-rhel8-operator:5.7.0-69.85e2026.5.7 | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: