Bug 1802381 (CVE-2020-1741) - CVE-2020-1741 openshift-ansible: cors allowed origin allows changing url protocol
Summary: CVE-2020-1741 openshift-ansible: cors allowed origin allows changing url prot...
Keywords:
Status: NEW
Alias: CVE-2020-1741
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1802394 1804302
Blocks: 1797390
TreeView+ depends on / blocked
 
Reported: 2020-02-13 03:39 UTC by Jason Shepherd
Modified: 2020-07-31 14:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
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.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Jason Shepherd 2020-02-13 03:39:09 UTC
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.

Comment 3 Jason Shepherd 2020-02-13 04:06:54 UTC
Mitigation:

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.

Comment 8 Jason Shepherd 2020-03-16 06:22:18 UTC
Filed a bug to get the documentation updated:

https://bugzilla.redhat.com/show_bug.cgi?id=1813799


Note You need to log in before you can comment on or make changes to this bug.