A flaw was found in openshift-logging LokiStack. The key used for caching is just the token, which is too broad. This issue allows a user with a token valid for one action to execute other actions as long as the authorization allowing the original action is still cached.
The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Openshift_logging | Redhat | * | * |
| RHOL-5.5-RHEL-8 | RedHat | openshift-logging/lokistack-gateway-rhel8:v0.1.0-327 | * |
| RHOL-5.6-RHEL-8 | RedHat | openshift-logging/lokistack-gateway-rhel8:v0.1.0-326 | * |
| RHOL-5.7-RHEL-8 | RedHat | openshift-logging/lokistack-gateway-rhel8:v0.1.0-325 | * |
Integrated circuits and hardware engines can expose accesses to assets (device configuration, keys, etc.) to trusted firmware or a software module (commonly set by BIOS/bootloader). This access is typically access-controlled. Upon a power reset, the hardware or system usually starts with default values in registers, and the trusted firmware (Boot firmware) configures the necessary access-control protection. A common weakness that can exist in such protection schemes is that access controls or policies are not granular enough. This condition allows agents beyond trusted agents to access assets and could lead to a loss of functionality or the ability to set up the device securely. This further results in security risks from leaked, sensitive, key material to modification of device configuration.