Windows kube-proxy LoadBalancer contention
Kubernetes
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| k8s.io/kubernetes Go |
|
|
Original description
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.
From the CVE record · kubernetes
References
- github.com/kubernetes/kubernetes/pull/99958Advisory
- groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOazPAgAJAdvisory
- security.netapp.com/advisory/ntap-20231221-0003
- nvd.nist.gov/vuln/detail/CVE-2021-25736
- github.com/kubernetes/kubernetes/commit/b014610de3e5cf1bb0f7844b5758d29fc18b75e6
- github.com/kubernetes/kubernetes
- security.netapp.com/advisory/ntap-20231221-0003
- github.com/advisories/GHSA-35c7-w35f-xwgh