Kubernetes requires an authentication mechanism to enforce users’ privileges. One method of authentication, bearer tokens, are opaque strings used to associate a user with their having successfully authenticated previously. Any user with possession of this token may masquerade as the original user (the “bearer”) without further authentication. Within Kubernetes, the bearer token is captured within the hyperkube kube-apiserver system logs at high verbosity levels (--v 10). A malicious user with access to the system logs on such a system could masquerade as any user who has previously logged into the system.
Created kubernetes tracking bugs for this issue: Affects: fedora-all [bug 1740435]
Upstream Issue: https://github.com/kubernetes/kubernetes/issues/81114
Upstream Patch: https://github.com/kubernetes/kubernetes/pull/81330/commits/010d8382
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 3.11 Via RHSA-2019:4052 https://access.redhat.com/errata/RHSA-2019:4052
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-11250
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.1 Via RHSA-2019:4087 https://access.redhat.com/errata/RHSA-2019:4087