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.
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.

cve-icon MITRE

Status: PUBLISHED

Assigner: kubernetes

Published:

Updated: 2025-02-13T16:27:50.253Z

Reserved: 2021-01-21T21:42:58.237Z

Link: CVE-2021-25736

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2023-10-30T03:15:07.653

Modified: 2025-02-13T17:15:28.237

Link: CVE-2021-25736

cve-icon Redhat

Severity : Moderate

Publid Date: 2021-05-10T00:00:00Z

Links: CVE-2021-25736 - Bugzilla