CVE-2020-8564
MEDIUMCVE-2020-8564 is a medium-severity (CVSS 5.5) CWE-532 vulnerability in github.com/kubernetes/kubernetes. O3 Security confirms whether CVE-2020-8564 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Kubernetes Sensitive Information leak via Log File
Real-World Exposure
github.com/kubernetes/kubernetes🐹github.com/kubernetes/kubernetes🐹github.com/kubernetes/kubernetes🐹k8s.io/kubernetesReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/kubernetes/kubernetes | ≥ 1.19.0&&< 1.19.3 | 1.19.3 |
| 🐹Go | github.com/kubernetes/kubernetes | ≥ 1.18.0&&< 1.18.10 | 1.18.10 |
| 🐹Go | github.com/kubernetes/kubernetes | all versions | 1.17.13 |
| 🐹Go | k8s.io/kubernetes | all versions | 1.20.0-alpha.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubernetes/kubernetes. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/kubernetes/kubernetes to 1.19.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-8564 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2020-8564 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2020-8564. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2020-8564 in your dependencies?
O3 detects CVE-2020-8564 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.