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.
Solution:
Link | Tags |
---|---|
https://github.com/kubernetes/kubernetes/pull/99958 | third party advisory |
https://groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOazPAgAJ | third party advisory mailing list |
https://security.netapp.com/advisory/ntap-20231221-0003/ |