Information disclosure in Kubernetes
CVE-2020-8565
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.7 (Medium). Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.005, 44.6th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Kubernetes — versions <= 1.19.3, <= 1.18.10, <= 1.17.13
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 4 other repositories (adavarski/HomeLab-k8s-DevSecOps-playground, adavarski/HomeLab-Proxmox-k8s-DevSecOps-playground, ARPSyndicate/cvemon, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- Multiple secret leaks when verbose logging is enabled (mailing-list, Patch, Mailing List, Third Party Advisory)
- github.com/kubernetes/kubernetes/issues/95623 (Third Party Advisory)