GHSA-qh36-44jv-c8xj
Potential proxy IP restriction bypass in Kubernetes
Details
As mitigations to a report from 2019 and CVE-2020-8555, Kubernetes attempts to prevent proxied connections from accessing link-local or localhost networks when making user-driven connections to Services, Pods, Nodes, or StorageClass service providers. As part of this mitigation Kubernetes does a DNS name resolution check and validates that response IPs are not in the link-local (169.254.0.0/16) or localhost (127.0.0.0/8) range. Kubernetes then performs a second DNS resolution without validation for the actual connection. If a non-standard DNS server returns different non-cached responses, a user may be able to bypass the proxy IP restriction and access private networks on the control plane. All versions of Kubernetes are impacted, and there is no fix in place.
Are you affected?
Enter the version of the package you're using.
Affected packages
1.21.0No fixed version published yet for k8s.io/kubernetes (go modules). Pin to a known-safe version or switch to an alternative.
1.20.0No fixed version published yet for k8s.io/kubernetes (go modules). Pin to a known-safe version or switch to an alternative.
1.19.0No fixed version published yet for k8s.io/kubernetes (go modules). Pin to a known-safe version or switch to an alternative.
0No fixed version published yet for k8s.io/kubernetes (go modules). Pin to a known-safe version or switch to an alternative.
References
- https://nvd.nist.gov/vuln/detail/CVE-2020-8562[ADVISORY]
- https://github.com/kubernetes/kubernetes/issues/101493[WEB]
- https://github.com/kubernetes/kubernetes/issues/101493#issuecomment-2272095629[WEB]
- https://github.com/kubernetes/kubernetes[PACKAGE]
- https://groups.google.com/g/kubernetes-security-announce/c/-MFX60_wdOY[WEB]
- https://kubernetes.io/blog/2026/05/26/reconciling-unfixed-kubernetes-cves[WEB]
- https://security.netapp.com/advisory/ntap-20220225-0002[WEB]