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.
Metrics
Affected Vendors & Products
References
History
Thu, 13 Feb 2025 16:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | 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. |

Status: PUBLISHED
Assigner: kubernetes
Published: 2023-10-30T02:19:48.916Z
Updated: 2025-02-13T16:27:50.253Z
Reserved: 2021-01-21T21:42:58.237Z
Link: CVE-2021-25736

No data.

Status : Modified
Published: 2023-10-30T03:15:07.653
Modified: 2025-02-13T17:15:28.237
Link: CVE-2021-25736
