title: 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.
problem types: CWE-532 Information Exposure Through Log Files
affected:
{
product: Kubernetes
vendor: Kubernetes
versions:
status: affected, version: <= 1.19.3
status: affected, version: <= 1.18.10
status: affected, version: <= 1.17.13
status: affected, version: < 1.20.0-alpha2
}
metrics:
cvssV3_1: [
attackComplexity: HIGH
attackVector: LOCAL
availabilityImpact: NONE
baseScore: 4.7
baseSeverity: MEDIUM
confidentialityImpact: HIGH
integrityImpact: NONE
privilegesRequired: LOW
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
version: 3.1
]
workarounds: Do not enable verbose logging in production (log level >= 9), limit access to logs.