CVE-2021-25736

low-risk
Published 2023-10-30

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.

Do I need to act?

-
0.08% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.8/10 Medium
NETWORK / HIGH complexity

Affected Products (1)

Affected Vendors

Kubernetes

References (6)

Third Party Advisory https://github.com/kubernetes/kubernetes/pull/99958
Mailing List https://groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOaz...
https://security.netapp.com/advisory/ntap-20231221-0003/
Third Party Advisory https://github.com/kubernetes/kubernetes/pull/99958
Mailing List https://groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOaz...
https://security.netapp.com/advisory/ntap-20231221-0003/
23
/ 100
low-risk
Severity 18/34 · Moderate
Exploitability 0/34 · Minimal
Exposure 5/34 · Minimal