REDHAT-BUG-1740434
First published: Tue Aug 13 2019(Updated: )
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.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Kubernetes API Server |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1740435
- https://github.com/kubernetes/kubernetes/issues/81114
- https://github.com/kubernetes/kubernetes/pull/81330/commits/010d8382
- https://access.redhat.com/errata/RHSA-2019:4052
- https://access.redhat.com/security/cve/cve-2019-11250
- https://access.redhat.com/errata/RHSA-2019:4087
- https://bugzilla.redhat.com/show_bug.cgi?id=1740434
Frequently Asked Questions
What is the severity of REDHAT-BUG-1740434?
The severity of REDHAT-BUG-1740434 is considered high due to the risk of unauthorized access using bearer tokens.
How do I fix REDHAT-BUG-1740434?
To fix REDHAT-BUG-1740434, ensure that bearer tokens are properly managed and implement additional security controls such as short token lifetimes.
What impact does REDHAT-BUG-1740434 have on Kubernetes security?
REDHAT-BUG-1740434 compromises Kubernetes security by allowing unauthorized users to impersonate legitimate users if they gain access to bearer tokens.
Is REDHAT-BUG-1740434 limited to specific versions of Kubernetes?
Yes, REDHAT-BUG-1740434 affects specific versions of the Kubernetes kube-apiserver that utilize bearer token authentication.
How can I monitor for exploitation of REDHAT-BUG-1740434?
You can monitor for exploitation of REDHAT-BUG-1740434 by tracking suspicious activity and unauthorized access attempts related to bearer token usage.
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2019-11250
- agent/source
- agent/references
- agent/severity
- agent/description
- agent/event
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/kubernetes
- canonical/kubernetes api server