CVE-2020-8565

Incomplete fix for CVE-2019-11250 allows for token leak in logs when logLevel >= 9

Description

In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects <= v1.19.3, <= v1.18.10, <= v1.17.13, < v1.20.0-alpha2.

Remediation

Workaround:

  • Do not enable verbose logging in production (log level >= 9), limit access to logs.

Category

4.7
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.06%
Third-Party Advisory github.com Third-Party Advisory google.com
Affected: Kubernetes Kubernetes
Published at:
Updated at:

References

Link Tags
https://groups.google.com/g/kubernetes-security-discuss/c/vm-HcrFUOCs/m/36utxAM5CwAJ mailing list third party advisory patch
https://github.com/kubernetes/kubernetes/issues/95623 third party advisory

Frequently Asked Questions

What is the severity of CVE-2020-8565?
CVE-2020-8565 has been scored as a medium severity vulnerability.
How to fix CVE-2020-8565?
As a workaround for remediating CVE-2020-8565: Do not enable verbose logging in production (log level >= 9), limit access to logs.
Is CVE-2020-8565 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-8565 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-8565?
CVE-2020-8565 affects Kubernetes Kubernetes.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.