First published: Tue Jul 16 2019(Updated: )
In the default configuration, OpenShift Container Platform 4 allows users with access to create pods the ability to schedule workloads on master nodes. Pods with permission to access the host network, running on master nodes, can retrieve security credentials for the master AWS IAM role, allowing management access to AWS resources. Pod access to the host network can be granted with the hostnetwork SCC. Original Bug: <a class="bz_bug_link bz_secure " title="" href="show_bug.cgi?id=1729242">https://bugzilla.redhat.com/show_bug.cgi?id=1729242</a> Upstream Fix: <a href="https://github.com/openshift/cluster-kube-apiserver-operator/pull/524">https://github.com/openshift/cluster-kube-apiserver-operator/pull/524</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat OpenShift Container Platform for IBM LinuxONE |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1730161 is considered critical due to the potential of unauthorized access to sensitive AWS IAM roles.
To fix REDHAT-BUG-1730161, adjust the security context constraints to restrict pod scheduling on master nodes.
REDHAT-BUG-1730161 affects users of the OpenShift Container Platform 4 with permissions to create pods.
The implications of REDHAT-BUG-1730161 include potential exposure of sensitive security credentials and elevated privileges for unauthorized users.
To mitigate REDHAT-BUG-1730161, limit access for users who can create pods and monitor pod activity closely.