# CVE-2020-8564: GO-2021-0066 - Sensitive information leak via log file in k8s.io/kubernetes

Source: https://junglewise.ai/threats/cve-2020-8564-kubernetes-sensitive-information-leak-via-log-file  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2021-04-14  
License: CC BY 4.0 with a link back

CVE-2020-8564 · Severity: low · CVSS 3.1 · Published 2021-04-14

Sensitive information leak via log file in k8s.io/kubernetes

Technologies: [github.com/kubernetes/kubernetes (Go)](https://junglewise.ai/threats/technologies/github-com-kubernetes-kubernetes), [k8s.io/kubernetes (Go)](https://junglewise.ai/threats/technologies/k8s-io-kubernetes). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2020-8564 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2020-8564 being exploited in the wild.

**How severe is CVE-2020-8564?** Low severity, with a CVSS score of 3.1, published 14 April 2021.

**Which products and versions are affected?** github.com/kubernetes/kubernetes (Go) SEMVER:introduced=1.19.0,fixed=1.19.3; k8s.io/kubernetes (Go) SEMVER:introduced=0,fixed=1.20.0-alpha.1.

**Is there a fix for CVE-2020-8564?** Yes. github.com/kubernetes/kubernetes (Go): upgrade to 1.19.3 or later; k8s.io/kubernetes (Go): upgrade to 1.20.0-alpha.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2020-8564?** Check whether you run github.com/kubernetes/kubernetes (Go) or k8s.io/kubernetes (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/kubernetes/kubernetes (Go): upgrade to 1.19.3 or later

  ```sh
  go get github.com/kubernetes/kubernetes@v1.19.3
  ```

- k8s.io/kubernetes (Go): upgrade to 1.20.0-alpha.1 or later

  ```sh
  go get k8s.io/kubernetes@v1.20.0-alpha.1
  ```


## Affected products

- github.com/kubernetes/kubernetes (Go) SEMVER:introduced=1.19.0,fixed=1.19.3
- k8s.io/kubernetes (Go) SEMVER:introduced=0,fixed=1.20.0-alpha.1

## Identifiers

- CVE-2020-8564
- GHSA-8mjg-8c8g-6h85
- GO-2021-0066

## Related threats

- [kube-controller-manager is vulnerable to half-blind Server Side Request Forgery through in-tree Portworx StorageClass](https://junglewise.ai/threats/cve-2025-13281-kube-controller-manager-is-vulnerable-to-half-blind-server-side)
- [GO-2025-3915 - Kubernetes Nodes can delete themselves by adding an OwnerReference in k8s.io/kubernetes](https://junglewise.ai/threats/cve-2025-5187-kubernetes-nodes-can-delete-themselves-by-adding-an-ownerreference)
- [GO-2025-3774 - Kubernetes allows nodes to bypass dynamic resource allocation authorization checks in k8s.io/kubernetes](https://junglewise.ai/threats/cve-2025-4563-kubernetes-allows-nodes-to-bypass-dynamic-resource-allocation)
- [GO-2025-3645 - Kubernetes did not effectively clear service account credentials in k8s.io/kubernetes](https://junglewise.ai/threats/cve-2019-11243-kubernetes-did-not-effectively-clear-service-account-credentials)
- [GO-2025-3522 - Kubernetes allows Command Injection affecting Windows nodes via nodes/*/logs/query API in k8s.io/kubernetes](https://junglewise.ai/threats/cve-2024-9042-kubernetes-allows-command-injection-affecting-windows-nodes-via)