First published: Mon Oct 30 2023(Updated: )
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.
Credit: jordan@liggitt.net jordan@liggitt.net
Affected Software | Affected Version | How to fix |
---|---|---|
go/k8s.io/kubernetes | <1.21 | 1.21 |
All of | ||
Any of | ||
Kubernetes Kubernetes | >=1.18.0<1.18.18 | |
Kubernetes Kubernetes | >=1.19.0<1.19.10 | |
Kubernetes Kubernetes | >=1.20.0<1.20.6 | |
Microsoft Windows |
This issue has been fixed in the following versions: * v1.21.0 * v1.20.6 * v1.19.10 * v1.18.18
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2021-25736 is medium, with a severity value of 5.8.
CVE-2021-25736 affects Windows kube-proxy by unintentionally forwarding traffic to local processes listening on the same port as a LoadBalancer Service when the LoadBalancer controller does not set the 'status.loadBalancer.ingress[].ip' field.
CVE-2021-25736 affects version up to, but not including, 1.21 of k8s.io/kubernetes.
To fix CVE-2021-25736, update to a version of k8s.io/kubernetes that is 1.21 or newer.
You can find more information about CVE-2021-25736 at the following references: [link1], [link2], [link3].