CVE-2020-8554GHSA-J9WF-VVM6-4R9W
Kubernetes man in the middle using LoadBalancer or ExternalIPs
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 5 proofs of concept on GitHub
Summary
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typically be granted to users) of a LoadBalancer service can set the status.loadBalancer.ingress.ip to similar effect.
Timeline
- CVE published
- Record last updated
Affected versions
- Kubernetes Kubernetes
All versions
- k8s.io/kubernetesGo
through 1.22.0
References 15
kubernetes.io
groups.google.com
GitHub · kubernetes/kubernetes
lists.apache.org
- thread.html/rcafa485d63550657f068775801aeb706b7a07140a8ebbdef822b3bb3@<commits.druid.apache.org>
- thread.html/r0c76b3d0be348f788cd947054141de0229af00c540564711e828fd40@<commits.druid.apache.org>
- thread.html/rdb223e1b82e3d7d8e4eaddce8dd1ab87252e3935cc41c859f49767b6@<commits.druid.apache.org>
- thread.html/r1975078e44d96f2a199aa90aa874b57a202eaf7f25f2fde6d1c44942@<commits.druid.apache.org>