CVE-2020-8563 Secret leaks in logs for vSphere Provider kube-controller-manager
Medium 4.7
Published
Updated
Check this codebase for CVE-2020-8563 and fix it if it is affected.
What it is: CVE-2020-8563 is a medium-severity vulnerability in Kubernetes Kubernetes, published on 7 Dec 2020.
Exploitation: There is no known exploitation of CVE-2020-8563 in the wild and no public exploit code.
Affected packages and fixed versions:
- github.com/kubernetes/kubernetes (Go): affected all versions; fixed in 1.19.3
- github.com/kubernetes/kubernetes (Go): affected all versions; fixed in 1.19.3
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.19.3
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2020-8563/ (Markdown: https://insights.sbomify.com/CVE-2020-8563/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2020-8563?
CVE-2020-8563 is a medium-severity vulnerability in Kubernetes Kubernetes, published on 7 Dec 2020.
Official description
In Kubernetes clusters using VSphere as a cloud provider, with a logging level set to 4 or above, VSphere cloud credentials will be leaked in the cloud controller manager's log. This affects < v1.19.3.
Weakness: CWE-532
Which versions are affected by CVE-2020-8563?
3 open source packages ship an affected version, including github.com/kubernetes/kubernetes and k8s.io/kubernetes. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/kubernetes/kubernetes Go | All versions | 1.19.3 |
github.com/kubernetes/kubernetes Go | All versions | 1.19.3 |
k8s.io/kubernetes Go | All versions | 1.19.3 |
Linux distribution packages (4)
openshift Red Hat:openshift:4.6::el7 | All versions | 0:4.6.0-202012051246.p0.git.94231.efc9027.el7 |
openshift-hyperkube Red Hat:openshift:4.6::el7 | All versions | 0:4.6.0-202012051246.p0.git.94231.efc9027.el7 |
openshift Red Hat:openshift:4.6::el8 | All versions | 0:4.6.0-202012051246.p0.git.94231.efc9027.el8 |
openshift-hyperkube Red Hat:openshift:4.6::el8 | All versions | 0:4.6.0-202012051246.p0.git.94231.efc9027.el8 |
Products include Kubernetes Kubernetes.
How do I fix CVE-2020-8563?
Upgrade github.com/kubernetes/kubernetes to 1.19.3 or later.
Is CVE-2020-8563 being exploited?
There is no known exploitation of CVE-2020-8563 in the wild and no public exploit code.
Other vulnerabilities in Kubernetes Kubernetes
- CVE-2018-1002105 Privilege Escalation in Kubernetes
- CVE-2017-1000056 Kubernetes Privilege Escalation
- CVE-2016-1906 Authorization bypass in Openshift
- CVE-2023-3676 Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation
- CVE-2023-3955 Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation
Sources
Also known as GHSA-5xfg-wv98-264m, GO-2024-2755, RHSA-2020:5260.