Openshift-logging: lokistack authorisation is cached too broadly
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | RHOL-5.5-RHEL-8 | affected |
|
||||||
| Red Hat | RHOL-5.6-RHEL-8 | affected |
|
||||||
| Red Hat | RHOL-5.7-RHEL-8 | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| RHOL-5.5-RHEL-8 | |||
| openshift-logging/lokistack-gateway-rhel8:v0.1.0-327 | cpe:/a:redhat:logging:5.5::el8 | RHSA-2023:5096 | 2023-09-20T00:00:00Z |
| RHOL-5.6-RHEL-8 | |||
| openshift-logging/lokistack-gateway-rhel8:v0.1.0-326 | cpe:/a:redhat:logging:5.6::el8 | RHSA-2023:5095 | 2023-09-20T00:00:00Z |
| RHOL-5.7-RHEL-8 | |||
| openshift-logging/lokistack-gateway-rhel8:v0.1.0-325 | cpe:/a:redhat:logging:5.7::el8 | RHSA-2023:4933 | 2023-09-13T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-54312 | 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.588% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|