medium
6.5
CWE
532
Advisory Published
Advisory Published
Advisory Published
Updated

CVE-2019-11250: Kubernetes client-go logs authorization headers at debug verbosity levels

First published: Mon Aug 12 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.

Credit: jordan@liggitt.net jordan@liggitt.net

Affected SoftwareAffected VersionHow to fix
go/k8s.io/kubernetes<1.16.0-beta.1
1.16.0-beta.1
go/k8s.io/client-go<0.17.0
0.17.0
redhat/atomic-openshift<0:3.11.157-1.git.0.dfe38da.el7
0:3.11.157-1.git.0.dfe38da.el7
redhat/openshift<0:4.1.27-201912021146.git.0.a40116f.el7
0:4.1.27-201912021146.git.0.a40116f.el7
Kubernetes Kubernetes<1.15.3
Kubernetes Kubernetes=1.15.3
Kubernetes Kubernetes=1.15.4-beta0
Kubernetes Kubernetes=1.16.0-alpha1
Kubernetes Kubernetes=1.16.0-alpha2
Kubernetes Kubernetes=1.16.0-alpha3
Kubernetes Kubernetes=1.16.0-beta1
Kubernetes Kubernetes=1.16.0-beta2
Redhat Openshift Container Platform=3.11
Redhat Openshift Container Platform=4.1

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.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2019-11250?

    The severity of CVE-2019-11250 is medium (6.5).

  • How can unauthorized users access credentials in CVE-2019-11250?

    Unauthorized users can access credentials in CVE-2019-11250 through logs or command output.

  • Which versions of Kubernetes components are affected by CVE-2019-11250?

    Kubernetes components (such as kube-apiserver) prior to v1.16.0 are affected by CVE-2019-11250.

  • How can I fix CVE-2019-11250?

    To fix CVE-2019-11250, you need to upgrade Kubernetes components to v1.16.0 or higher.

  • Where can I find more information about CVE-2019-11250?

    You can find more information about CVE-2019-11250 at the following references: [NVD](https://nvd.nist.gov/vuln/detail/CVE-2019-11250), [GitHub](https://github.com/kubernetes/kubernetes/issues/81114), and [Red Hat Advisory](https://access.redhat.com/errata/RHSA-2019:4052).

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203