Vulnerabilities · 2021 · Kubernetes
CVE-2021-25736
Kubernetes vulnerability
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 products
Kubernetes. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Kubernetes runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/kubernetes/kubernetes/pull/99958 · Third Party Advisory
- groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOazPAgAJ · Third Party Advisory
- security.netapp.com/advisory/ntap-20231221-0003/
- nvd.nist.gov/vuln/detail/CVE-2021-25736
- github.com/kubernetes/kubernetes/commit/b014610de3e5cf1bb0f7844b5758d29fc18b75e6
- security.netapp.com/advisory/ntap-20231221-0003
- github.com/advisories/GHSA-35c7-w35f-xwgh
- nvd.nist.gov/vuln/detail/CVE-2021-25736
- cve.org/CVERecord?id=CVE-2021-25736
More vulnerabilities in Kubernetes products
CVE-2024-5154CVE-2023-5528CVE-2023-5044CVE-2023-5043CVE-2023-3955CVE-2023-3893CVE-2023-3676CVE-2023-2878All 89
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.