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.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2023:4933 | vendor advisory |
https://access.redhat.com/errata/RHSA-2023:5095 | vendor advisory |
https://access.redhat.com/errata/RHSA-2023:5096 | vendor advisory |
https://access.redhat.com/security/cve/CVE-2023-4456 | vdb entry vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=2233087 | vendor advisory issue tracking |