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.
Workaround:
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state.
| Link | Tags |
|---|---|
| https://github.com/kubernetes/kubernetes/issues/101493 | mitigation third party advisory issue tracking |
| https://groups.google.com/g/kubernetes-security-announce/c/-MFX60_wdOY | third party advisory mailing list |
| https://security.netapp.com/advisory/ntap-20220225-0002/ | third party advisory |