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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-0665 | 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. |
Github GHSA |
GHSA-8cfg-vx93-jvxw | Kubernetes client-go vulnerable to Sensitive Information Leak via Log File |
Fixes
Solution
No solution given by the vendor.
Workaround
Do not enable verbose logging in production (log level >= 9), limit access to logs.
References
History
Wed, 16 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Status: PUBLISHED
Assigner: kubernetes
Published:
Updated: 2024-09-17T00:05:58.669Z
Reserved: 2020-02-03T00:00:00
Link: CVE-2020-8565
No data.
Status : Modified
Published: 2020-12-07T22:15:21.400
Modified: 2024-11-21T05:39:02.543
Link: CVE-2020-8565
OpenCVE Enrichment
No data.
EUVD
Github GHSA