CVE-2023-4456: Openshift-logging: lokistack authorisation is cached too broadly
First published: Mon Aug 21 2023(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat OpenShift Logging |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this flaw in openshift-logging LokiStack?
The vulnerability ID for this flaw is CVE-2023-4456.
What is the severity of CVE-2023-4456?
The severity of CVE-2023-4456 is medium with a CVSS score of 6.5.
What is the affected software for CVE-2023-4456?
The affected software for CVE-2023-4456 is Redhat Openshift Logging.
What is the impact of CVE-2023-4456?
CVE-2023-4456 allows a user with a valid token for one action to execute other actions as long as the authorization allowing the original action is still cached.
How can this vulnerability be fixed?
To fix CVE-2023-4456, it is recommended to update to the latest version of openshift-logging LokiStack.
- agent/author
- agent/type
- agent/first-publish-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2023-4456
- agent/references
- agent/weakness
- agent/severity
- agent/description
- agent/title
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/softwarecombine
- vendor/redhat
- canonical/red hat openshift logging