CVE-2020-8565

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

Published Dec 7, 2020 CVSS 3.1 · 4.7 Medium EPSS < 1% KEV · Not listed
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

Vendor Workaround

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

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD 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 Github GHSA GHSA-8cfg-vx93-jvxw Kubernetes client-go vulnerable to Sensitive Information Leak via Log File
History
Type Values Removed Values Added
Metrics epss

{'score': 0.00058}

epss

{'score': 0.0006}

Weaknesses

Sources

Status
PUBLISHED
Assigner
kubernetes
Published
Updated
Sep 17, 2024, 12:05 AM
Reserved
Feb 3, 2020, 12:00 AM
Status
Modified
Published
Dec 7, 2020, 10:15 PM
Modified
Jun 17, 2026, 3:26 AM
Severity
Moderate
Public date
Oct 14, 2020, 12:00 AM