CVE-2020-8554: Kubernetes man in the middle using LoadBalancer or ExternalIPs
Noroxi assessment
Priority: Monitor (action score 23/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 8.7% (FIRST EPSS); higher than 95.2% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: kubernetes (Debian:13) 1.31.4+ds-1; atomic-enterprise-service-catalog (Red Hat:openshift:3.11::el7) 1:3.11.374-1.git.1675.738abcc.el7; atomic-enterprise-service-catalog-svcat (Red Hat:openshift:3.11::el7) 1:3.11.374-1.git.1675.738abcc.el7.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to kubernetes (Debian:13) 1.31.4+ds-1; atomic-enterprise-service-catalog (Red Hat:openshift:3.11::el7) 1:3.11.374-1.git.1675.738abcc.el7; atomic-enterprise-service-catalog-svcat (Red Hat:openshift:3.11::el7) 1:3.11.374-1.git.1675.738abcc.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 21, 2021
- Updated
- Jun 16, 2026
- EPSS
- 8.7% · 95th percentile
- CWE
- CWE-283
Report tools
Action score
23
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 8.7%
CNA vs NVD score
- NVD
- 5.0
- CNA · kubernetes
- 6.3
- 1.3 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| kubernetes | kubernetes | cpe:2.3:a:kubernetes:kubernetes |
| oracle | communications cloud native core network slice selection function | cpe:2.3:a:oracle:communications_cloud_native_core_network_slice_selection_function |
| oracle | communications cloud native core policy | cpe:2.3:a:oracle:communications_cloud_native_core_policy |
| oracle | communications cloud native core service communication proxy | cpe:2.3:a:oracle:communications_cloud_native_core_service_communication_proxy |
Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.
Kubernetes Kubernetes
- all versionsaffected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kubernetes kubernetesall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | kubernetes | before 1.31.4+ds-1 | 1.31.4+ds-1 |
| Go | k8s.io/kubernetes | up to and including 1.22.0 | — |
| Red Hat:openshift:3.11::el7 | atomic-enterprise-service-catalog | before 1:3.11.374-1.git.1675.738abcc.el7 | 1:3.11.374-1.git.1675.738abcc.el7 |
| Red Hat:openshift:3.11::el7 | atomic-enterprise-service-catalog-svcat | before 1:3.11.374-1.git.1675.738abcc.el7 | 1:3.11.374-1.git.1675.738abcc.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-cluster-autoscaler | before 0:3.11.374-1.git.0.2996f62.el7 | 0:3.11.374-1.git.0.2996f62.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-descheduler | before 0:3.11.374-1.git.299.f128e96.el7 | 0:3.11.374-1.git.299.f128e96.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-dockerregistry | before 0:3.11.374-1.git.481.e6a880c.el7 | 0:3.11.374-1.git.481.e6a880c.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-excluder | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hyperkube | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hypershift | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-master | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-metrics-server | before 0:3.11.374-1.git.53.9df25a9.el7 | 0:3.11.374-1.git.53.9df25a9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node-problem-detector | before 0:3.11.374-1.git.263.28335fb.el7 | 0:3.11.374-1.git.263.28335fb.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-pod | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-sdn-ovs | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-service-idler | before 0:3.11.374-1.git.15.523a1f7.el7 | 0:3.11.374-1.git.15.523a1f7.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-template-service-broker | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-tests | before 0:3.11.374-1.git.0.ebd3ee9.el7 | 0:3.11.374-1.git.0.ebd3ee9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-web-console | before 0:3.11.374-1.git.647.9e78d83.el7 | 0:3.11.374-1.git.647.9e78d83.el7 |
+11
Same product
kubernetes: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1002105In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in…65This week
- CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port55Plan
- CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with…42Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-8565Dec 7, 2020 · Incomplete fix for CVE-2019-11250 allows for token leak in logs when logLevel >= 922Monitor
- ← EarlierCVE-2020-8566Dec 7, 2020 · Ceph RBD adminSecrets exposed in logs when loglevel >= 422Monitor
- Later →CVE-2021-25735Sep 6, 2021 · Validating Admission Webhook does not observe some previous fields28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:kubernetes | 1.31.4+ds-1 · Debian:13 | Package registry (OSV) |
| red hat:atomic-enterprise-service-catalog | 1:3.11.374-1.git.1675.738abcc.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-enterprise-service-catalog-svcat | 1:3.11.374-1.git.1675.738abcc.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift | 0:3.11.374-1.git.0.ebd3ee9.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients | 0:3.11.374-1.git.0.ebd3ee9.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients-redistributable | 0:3.11.374-1.git.0.ebd3ee9.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-cluster-autoscaler | 0:3.11.374-1.git.0.2996f62.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-descheduler | 0:3.11.374-1.git.299.f128e96.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-docker-excluder | 0:3.11.374-1.git.0.ebd3ee9.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-dockerregistry | 0:3.11.374-1.git.481.e6a880c.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-excluder | 0:3.11.374-1.git.0.ebd3ee9.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hyperkube | 0:3.11.374-1.git.0.ebd3ee9.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hypershift | 0:3.11.374-1.git.0.ebd3ee9.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×5
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 5 repositories | 2020-12-01 → 2021-02-09 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-52 d
- Published
- TodayNov 16, 2026+2125 d
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0638 · Nov 15, 2023(Microsoft Güvenlik Güncellemesi)
- TR-22-0069 · Jan 20, 2022(Oracle Güvenlik Zafiyeti)
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-283 · Unverified OwnershipCVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- kubernetes.io/blog/2026/05/26/reconciling-unfixed-kubernetes-cves/
- lists.apache.org/thread.html/r0c76b3d0be348f788cd947054141de0229af00c540564711e828fd40%40%3Ccommits.druid.apache.org%3E
- lists.apache.org/thread.html/r1975078e44d96f2a199aa90aa874b57a202eaf7f25f2fde6d1c44942%40%3Ccommits.druid.apache.org%3E
- lists.apache.org/thread.html/rcafa485d63550657f068775801aeb706b7a07140a8ebbdef822b3bb3%40%3Ccommits.druid.apache.org%3E
- lists.apache.org/thread.html/rdb223e1b82e3d7d8e4eaddce8dd1ab87252e3935cc41c859f49767b6%40%3Ccommits.druid.apache.org%3E
- www.oracle.com//security-alerts/cpujul2021.html
- www.oracle.com/security-alerts/cpuapr2022.html
- www.oracle.com/security-alerts/cpujan2022.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.