First published: Tue Feb 09 2021(Updated: )
When running OpenShift with Red Hat supported network types, applications in the cluster are blocked from sending traffic to ports 22623 or 22624 via iptables rules injected into the pod. This ensures that no unprivileged workloads are able to access the Machine Config Server (MCS) and download ignition configuration, which may contain sensitive information. Unfortunately, this security measure is implemented within the code for the network plugins, so a cluster that uses another network plugin (like Calico, for example), would not have this protection mechanism in place. In other words, all applications running on OpenShift clusters not using Red Hat supported network types will be able to access the MCS.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat OpenShift Origin |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1926568 is considered high as it prevents unprivileged workloads from accessing the Machine Config Server.
To fix REDHAT-BUG-1926568, ensure that your network policies allow access to ports 22623 and 22624 as needed.
REDHAT-BUG-1926568 affects applications running on Red Hat OpenShift with certain network types configured.
The impact of REDHAT-BUG-1926568 is that applications in the OpenShift cluster are blocked from sending traffic to the Machine Config Server.
REDHAT-BUG-1926568 specifically affects the Red Hat OpenShift product without specifying particular versions.