REDHAT-BUG-1802381: Low severity Red Hat OpenShift Container Platform vulnerability
OpenShift Container Platform (OCP) 3.11 was too permissive in the way it specified CORS allowed origins during installation. An attacker able to man-in-the-middle the connection between the user's browser and the openshift console could use this flaw to perform a phishing attack.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
During installation or in the console/master configuration, do not use wildcard or overly permissive CORS origin settings. Configure the CORS allowed origins to a precise list of trusted origin URLs to prevent cross-origin requests from arbitrary origins.
OpenShift Container Platform (OCP) 3.11 CORS allowed origins = restrict to explicit trusted origins (no wildcard/permissive origin) - Compensating control
Restrict access to the OpenShift console to trusted networks or IP addresses (for example via firewall rules, VPN, or network ACLs) and ensure console traffic uses valid TLS certificates to reduce the risk of man-in-the-middle attacks.
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-1802381?
The severity of REDHAT-BUG-1802381 is considered high due to the potential for phishing attacks via man-in-the-middle exploitation.
How do I fix REDHAT-BUG-1802381?
To fix REDHAT-BUG-1802381, ensure that CORS allowed origins are configured securely in your OpenShift Container Platform deployment.
What are the potential impacts of REDHAT-BUG-1802381?
The potential impacts of REDHAT-BUG-1802381 include unauthorized access and exposure to phishing attacks targeting users of the OpenShift console.
Which version of OpenShift Container Platform is affected by REDHAT-BUG-1802381?
OpenShift Container Platform version 3.11 is affected by REDHAT-BUG-1802381.
Can REDHAT-BUG-1802381 lead to data breaches?
Yes, if exploited, REDHAT-BUG-1802381 can lead to data breaches through phishing tactics used by attackers.