Bug 2300037 (CVE-2024-7128)
| Summary: | CVE-2024-7128 openshift-console: Unauthenticated Data Exposure | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Michal Findra <mfindra> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | dahernan |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
A flaw was found in the OpenShift console. Several endpoints in the application use the authHandler() and authHandlerWithUser() middleware functions. When the default authentication provider ("openShiftAuth") is set, these functions do not perform any authentication checks, relying instead on the targeted service to handle authentication and authorization. This issue leads to various degrees of data exposure due to a lack of proper credential verification.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2025:4427 https://access.redhat.com/errata/RHSA-2025:4427 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2025:4723 https://access.redhat.com/errata/RHSA-2025:4723 |
Several endpoints use the authHandler() and authHandlerWithUser() middleware functions. When the authentication provider is set to the default ("openShiftAuth"), no verification of authentication is actually performed by these functions, leaving the authentication/authorization checks to be performed by the targeted service. The following endpoints are using the aforementioned middleware functions without checking if the user provided valid credentials lead to various degrees of data exposure: /api/console/monitoring-dashboard-config /api/console/knative-event-sources /api/console/knative-channels /api/check-updates /api/console/version /api/copy-login-commands /api/gitops /api/plugins/ /api/metrics /api/metrics/usage