CVE-2020-8559: Privilege escalation from compromised node to cluster
Noroxi assessment
Priority: Monitor (action score 29/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: 6.1% (FIRST EPSS); higher than 93.4% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: kubernetes (Debian:12) 1.18.5-1; k8s.io/apimachinery (Go) 0.17.9, 0.18.7-rc.0, 0.18.7; k8s.io/kubernetes (Go) 1.17.9, 1.18.7, 1.16.13.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to kubernetes (Debian:12) 1.18.5-1; k8s.io/apimachinery (Go) 0.17.9, 0.18.7-rc.0, 0.18.7; k8s.io/kubernetes (Go) 1.17.9, 1.18.7, 1.16.13 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
The Kubernetes kube-apiserver in versions v1.6-v1.15, and versions prior to v1.16.13, v1.17.9 and v1.18.6 are vulnerable to an unvalidated redirect on proxied upgrade requests that could allow an attacker to escalate privileges from a node compromise to a full cluster compromise.
- Published
- Jul 22, 2020
- Updated
- Jun 16, 2026
- EPSS
- 6.1% · 93th percentile
- CWE
- CWE-601
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.1%
CNA vs NVD score
- NVD
- 6.8
- CNA · kubernetes
- 6.4
- 0.4 point gap
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kubernetes kubernetes1.6.0 and later · up to 1.15.0 inclusive
- kubernetes kubernetes1.16.0 and later · before 1.16.13
- kubernetes kubernetes1.17.0 and later · before 1.17.9
- kubernetes kubernetes1.18.0 and later · before 1.18.6
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
- 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12, 1.13, 1.14, 1.15affected
- 1.16 and later · up to and including 1.16.12affected
- 1.17 and later · up to and including 1.17.8affected
- 1.18 and later · up to and including 1.18.5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | kubernetes | before 1.18.5-1 | 1.18.5-1 |
| Go | k8s.io/apimachinery | from 0.17.0 · before 0.17.9 | 0.17.9 |
| Go | k8s.io/apimachinery | from 0.18.0 · before 0.18.7-rc.0 | 0.18.7-rc.0 |
| Go | k8s.io/apimachinery | from 0.18.0 · before 0.18.7 | 0.18.7 |
| Go | k8s.io/apimachinery | before 0.16.13 | 0.16.13 |
| Go | k8s.io/kubernetes | from 1.17.0 · before 1.17.9 | 1.17.9 |
| Go | k8s.io/kubernetes | from 1.18.0 · before 1.18.7 | 1.18.7 |
| Go | k8s.io/kubernetes | before 1.16.13 | 1.16.13 |
| Red Hat:openshift:3.11::el7 | atomic-openshift | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-excluder | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hyperkube | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hypershift | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-master | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-pod | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-sdn-ovs | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-template-service-broker | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-tests | before 0:3.11.346-1.git.0.ea10721.el7 | 0:3.11.346-1.git.0.ea10721.el7 |
| Red Hat:openshift:4.4::el7 | openshift | before 0:4.4.0-202012052258.p0.git.0.0fd57a4.el7 | 0:4.4.0-202012052258.p0.git.0.0fd57a4.el7 |
| Red Hat:openshift:4.4::el7 | openshift-hyperkube | before 0:4.4.0-202012052258.p0.git.0.0fd57a4.el7 | 0:4.4.0-202012052258.p0.git.0.0fd57a4.el7 |
| Red Hat:openshift:4.4::el8 | openshift | before 0:4.4.0-202012052258.p0.git.0.0fd57a4.el8 | 0:4.4.0-202012052258.p0.git.0.0fd57a4.el8 |
+10
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 the65This 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-2019-11254Apr 1, 2020 · Kubernetes API Server denial of service vulnerability from malicious YAML payloads27Monitor
- ← EarlierCVE-2020-8555Jun 5, 2020 · Kubernetes kube-controller-manager SSRF26Monitor
- Later →CVE-2019-11252Jul 23, 2020 · Credential leakage when failing to mount26Monitor
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.18.5-1 · Debian:12 | Package registry (OSV) |
| Go:k8s.io/apimachinery | 0.16.13 | Package registry (OSV) |
| Go:k8s.io/apimachinery | 0.17.9 | Package registry (OSV) |
| Go:k8s.io/apimachinery | 0.18.7 | Package registry (OSV) |
| Go:k8s.io/apimachinery | 0.18.7-rc.0 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.16.13 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.17.9 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.18.7 | Package registry (OSV) |
| red hat:atomic-openshift | 0:3.11.346-1.git.0.ea10721.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients | 0:3.11.346-1.git.0.ea10721.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients-redistributable | 0:3.11.346-1.git.0.ea10721.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-docker-excluder | 0:3.11.346-1.git.0.ea10721.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-excluder | 0:3.11.346-1.git.0.ea10721.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:ignition | 0:2.6.0-5.rhaos4.6.git947598e.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:ignition-debuginfo | 0:2.6.0-5.rhaos4.6.git947598e.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:ignition-debugsource | 0:2.6.0-5.rhaos4.6.git947598e.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:ignition-validate | 0:2.6.0-5.rhaos4.6.git947598e.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:ignition-validate-debuginfo | 0:2.6.0-5.rhaos4.6.git947598e.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:openshift | 0:4.6.0-202010022112.p0.git.94033.ef41184.el7 · Red Hat:openshift:4.6::el7 | Package registry (OSV) |
| red hat:openshift-hyperkube | 0:4.6.0-202010022112.p0.git.94033.ef41184.el7 · Red Hat:openshift:4.6::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 ×2
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 | stars:20 | 2020-07-22 |
| Proof-of-concept repository on GitHub | stars:53 | 2020-07-22 |
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 PoCsame day
- Published
- TodayNov 3, 2026+2296 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Wouter ter MaatOffensi
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
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-20-1006 · Dec 4, 2020(OpenShift Güvenlik Güncellemesi)
- TR-20-797 · Sep 30, 2020(IBM Cloud Private Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.