Vulnerability in k8s.io/kubernetes (CVE-2020-8562)
Summary
Vulnerability in k8s.io/kubernetes (CVE-2020-8562). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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. All versions of Kubernetes are impacted, and there is no fix in place.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-8562 has been found in k8s.io/kubernetes.
Risk of unauthorized operations or information disclosure. CVSS score: 2.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "k8s.io/kubernetes CVE-2020-8562" on the vendor's site.
CVE-2020-8562 (k8s.io/kubernetes) — CWE-367 / CVSS v3 2.2
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-367) exists in k8s.io/kubernetes.
Check the vendor advisory for the affected versions of k8s.io/kubernetes.
Severity: Low (CVSS 2.2/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'k8s.io/kubernetes' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'k8s.io/kubernetes' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
k8s.io/kubernetesを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2020-8562 kubernetes Fixed in: 1.20.5+really1.20.2-1
References
- advisory security.netapp.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web groups.google.com
- web kubernetes.io
- web github.com
- web security.netapp.com
- web kubernetes.io
- web github.com