Red Hat OpenShift Enterprise 3.2, when multi-tenant SDN is enabled and a build is run in a namespace that would normally be isolated from pods in other namespaces, allows remote authenticated users to access network resources on restricted pods via an s2i build with a builder image that (1) contains ONBUILD commands or (2) does not contain a tar binary.
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.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 | * |
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: