Kube-proxy on Windows can unintentionally forward traffic to local processes listening on the same port (“spec.ports[*].port”) as a LoadBalancer Service when the LoadBalancer controller does not set the “status.loadBalancer.ingress[].ip” field. Clusters where the LoadBalancer controller sets the “status.loadBalancer.ingress[].ip” field are unaffected.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Kubernetes | Kubernetes | 1.18.0 (including) | 1.18.18 (excluding) |
| Kubernetes | Kubernetes | 1.19.0 (including) | 1.19.10 (excluding) |
| Kubernetes | Kubernetes | 1.20.0 (including) | 1.20.6 (excluding) |
| Red Hat OpenShift Container Platform 4.7 | RedHat | openshift4-wincw/windows-machine-config-operator-bundle:v2.0.1-8 | * |
| Red Hat OpenShift Container Platform 4.7 | RedHat | openshift4-wincw/windows-machine-config-rhel8-operator:2.0.1-6 | * |
References
- https://github.com/kubernetes/kubernetes/pull/99958
- https://groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOazPAgAJ
- https://security.netapp.com/advisory/ntap-20231221-0003/
- https://github.com/kubernetes/kubernetes/pull/99958
- https://groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOazPAgAJ
- https://security.netapp.com/advisory/ntap-20231221-0003/