Red Hat OpenShift Enterprise 3.2 and 3.1 do not properly validate the origin of a request when anonymous access is granted to a service/proxy or pod/proxy API for a specific pod, which allows remote attackers to access API credentials in the web browser localStorage via an access_token in the query parameter.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Openshift | Redhat | 3.1 (including) | 3.1 (including) |
Openshift | Redhat | 3.2 (including) | 3.2 (including) |
Red Hat OpenShift Container Platform 3.2 | RedHat | atomic-openshift-0:3.2.0.44-1.git.0.a4463d9.el7 | * |
Red Hat OpenShift Container Platform 3.2 | RedHat | nodejs-node-uuid-0:1.4.7-1.el7 | * |
Red Hat OpenShift Enterprise 3.1 | RedHat | atomic-openshift-0:3.1.1.6-8.git.64.80b61da.el7aos | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: