CVE-2020-8554: Kubernetes man in the middle using LoadBalancer or ExternalIPs
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.
Security readout for executives and security teams
Plain-English summary
This Kubernetes flaw can let a user with limited service-management rights redirect traffic meant for an external IP through a service they control. The business risk is strongest in shared or multi-tenant clusters where application teams can create or modify Services without tight controls.
Executive priority
Treat this as a priority hardening item for shared Kubernetes platforms, especially where teams self-service networking resources. It is not presented as an emergency zero-day in the bundle, but weak RBAC could turn it into meaningful traffic interception risk.
Technical view
CVE-2020-8554 affects Kubernetes API server behavior around Service externalIPs and LoadBalancer status IPs. A user who can create ClusterIP Services with spec.externalIPs, or privileged users who can patch LoadBalancer status, may intercept traffic to those IPs. CVSS is 6.3, with low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in Kubernetes clusters where non-admin users, tenants, CI systems, or operators can create Services with externalIPs or patch service/status. Single-tenant clusters with tightly controlled Service creation are lower risk, but should still be audited.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires Kubernetes credentials with specific Service creation or status-patching permissions, so this is mainly an insider, compromised-account, or tenant-isolation concern.
Researcher notes
Evidence indicates a Kubernetes authorization/design issue tracked publicly, with no universal fixed release identified in the supplied bundle. Focus validation on effective RBAC, admission behavior, and existing Service objects. Avoid assuming downstream distributions are fixed unless their advisories explicitly say so.
Mitigation direction
Audit RBAC for users allowed to create or update Kubernetes Services.
Restrict use of spec.externalIPs to trusted administrators only.
Do not grant service/status patch permissions except to trusted controllers.
Review Kubernetes vendor guidance for current recommended controls.
Harden multi-tenant clusters with admission policy around risky Service fields.
Validation and detection
List roles and bindings that allow create, update, or patch on Services.
Check whether any non-admin principals can modify service/status.
Inventory Services using spec.externalIPs across all namespaces.
Review LoadBalancer Services for unexpected ingress IP values.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-283: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-283 · source CWE mapping
Unverified Ownership
Unverified Ownership represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.