CVE-2020-8564 Docker config secrets leaked when file is malformed and loglevel >= 4
Medium 4.7
Published
Updated
Check this codebase for CVE-2020-8564 and fix it if it is affected.
What it is: CVE-2020-8564 is a medium-severity vulnerability in Kubernetes Kubernetes, published on 7 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8564 in the wild and no public exploit code.
Affected packages and fixed versions:
- github.com/kubernetes/kubernetes (Go): affected all versions; fixed in 1.17.13
- github.com/kubernetes/kubernetes (Go): affected all versions; fixed in 1.17.13
- github.com/kubernetes/kubernetes (Go): affected from 1.18.0; fixed in 1.18.10
- github.com/kubernetes/kubernetes (Go): affected from 1.18.0; fixed in 1.18.10
- github.com/kubernetes/kubernetes (Go): affected from 1.19.0; fixed in 1.19.3
- github.com/kubernetes/kubernetes (Go): affected from 1.19.0; fixed in 1.19.3
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.20.0-alpha.1
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.20.0-alpha.1
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.20.0-alpha.1
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-8564/ (Markdown: https://insights.sbomify.com/CVE-2020-8564/index.md)
Attackers can leak Docker registry credentials from malformed config files in Kubernetes clusters with verbose logging enabled.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-8564?
CVE-2020-8564 is a medium-severity vulnerability in Kubernetes Kubernetes, published on 7 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In Kubernetes clusters using a logging level of at least 4, processing a malformed docker config file will result in the contents of the docker config file being leaked, which can include pull secrets or other registry credentials. This affects < v1.19.3, < v1.18.10, < v1.17.13.
Weakness: CWE-532
Which versions are affected by CVE-2020-8564?
9 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.17.13 |
github.com/kubernetes/kubernetes Go | All versions | 1.17.13 |
github.com/kubernetes/kubernetes Go | From 1.18.0 | 1.18.10 |
github.com/kubernetes/kubernetes Go | From 1.18.0 | 1.18.10 |
github.com/kubernetes/kubernetes Go | From 1.19.0 | 1.19.3 |
github.com/kubernetes/kubernetes Go | From 1.19.0 | 1.19.3 |
3 more packages
k8s.io/kubernetes Go | All versions | 1.20.0-alpha.1 |
k8s.io/kubernetes Go | All versions | 1.20.0-alpha.1 |
k8s.io/kubernetes Go | All versions | 1.20.0-alpha.1 |
Linux distribution packages (13)
atomic-openshift Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-clients Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-clients-redistributable Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-docker-excluder Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-excluder Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-hyperkube Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-hypershift Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-master Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-node Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-pod Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-sdn-ovs Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-template-service-broker Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
atomic-openshift-tests Red Hat:openshift:3.11::el7 | All versions | 0:3.11.501-1.git.0.f8c4746.el7 |
Products include Kubernetes Kubernetes.
How do I fix CVE-2020-8564?
Upgrade github.com/kubernetes/kubernetes to a fixed version for your release line: 1.17.13, 1.18.10 or 1.19.3.
Is CVE-2020-8564 being exploited?
There is no known exploitation of CVE-2020-8564 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 DEBIAN-CVE-2020-8564, GHSA-8mjg-8c8g-6h85, GO-2021-0066, RHSA-2021:3193.