First published: Thu Feb 13 2020(Updated: )
A flaw was found in openshift-ansible. OpenShift Container Platform (OCP) 3.11 is 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. The main threat from this vulnerability is data confidentiality.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/openshift-ansible | <0:3.11.272-1.git.0.79ab6e9.el7 | 0:3.11.272-1.git.0.79ab6e9.el7 |
Redhat Openshift Container Platform | =3.11 |
Ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - ^(?i)https://my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ as the first will permit cross origin requests only if the host and protocol matches, whereas the second will permit a downgrade to http protocol for example.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2020-1741.
The severity of CVE-2020-1741 is medium, with a severity value of 5.9.
The affected software is openshift-ansible version 3.11.272-1.git.0.79ab6e9.el7.
An attacker, able to man-in-the-middle the connection between the user's browser and the openshift console, could exploit CVE-2020-1741.
Yes, a fix is available for CVE-2020-1741. Upgrade to openshift-ansible version 3.11.272-1.git.0.79ab6e9.el7 or higher.