CVE-2020-8565: medium-severity vulnerability in Kubernetes
Incomplete fix for CVE-2019-11250 allows for token leak in logs when logLevel >= 9
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.7epss 0.5%
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.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected products
Kubernetes · KubernetesRelated CVEs — Kubernetes
In the same product, most dangerous first.
CVE-2018-1002105CRITICALCVE-2018-1002105EPSS 87.0%CVE-2019-11248MEDIUMKubernetes kubelet exposes /debug/pprof info on healthz portEPSS 75.1%CVE-2019-11253HIGHKubernetes API Server JSON/YAML parsing vulnerable to resource exhaustion attackEPSS 25.9%CVE-2019-1002100MEDIUMCVE-2019-1002100EPSS 16.9%CVE-2017-1002101HIGHCVE-2017-1002101EPSS 13.3%CVE-2019-1002101MEDIUMkubectl cp path traversalEPSS 12.8%