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.
References
Link | Resource |
---|---|
https://github.com/kubernetes/kubernetes/pull/99958 | Third Party Advisory |
https://groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOazPAgAJ | Mailing List Third Party Advisory |
https://security.netapp.com/advisory/ntap-20231221-0003/ |
Configurations
Configuration 1 (hide)
AND |
|
History
21 Dec 2023, 22:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2023-10-30 03:15
Updated : 2024-02-05 00:01
NVD link : CVE-2021-25736
Mitre link : CVE-2021-25736
CVE.ORG link : CVE-2021-25736
JSON object : View
Products Affected
microsoft
- windows
kubernetes
- kubernetes
CWE