title: Windows kube-proxy LoadBalancer contention
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.
affected:
{
defaultStatus: unaffected
modules: Kube-Proxy
platforms: Windows
product: Kubernetes
repo: https://github.com/kubernetes/kubernetes
vendor: Kubernetes
versions:
lessThanOrEqual: v1.20.5, status: affected, version: 0, versionType: v1.20.5
}
metrics:
cvssV3_1: [
attackComplexity: HIGH
attackVector: NETWORK
availabilityImpact: NONE
baseScore: 5.8
baseSeverity: MEDIUM
confidentialityImpact: HIGH
integrityImpact: NONE
privilegesRequired: HIGH
scope: CHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
version: 3.1
]
format: CVSS
scenarios: GENERAL
solutions: This issue has been fixed in the following versions:
*
v1.21.0
*
v1.20.6
*
v1.19.10
*
v1.18.18