CVE-2019-11250: GO-2021-0065 - Unauthorized credential disclosure in k8s.io/kubernetes and k8s.io/client-go

CVE-2019-11250 · Severity: low · CVSS 3.1 · Published 2021-04-14

Unauthorized credential disclosure in k8s.io/kubernetes and k8s.io/client-go

Technologies: k8s.io/client-go (Go), k8s.io/kubernetes (Go). Vendors: Go.

Quick answers

Is CVE-2019-11250 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-11250 being exploited in the wild.
How severe is CVE-2019-11250?
Low severity, with a CVSS score of 3.1, published 14 April 2021.
Which products and versions are affected?
k8s.io/client-go (Go) SEMVER:introduced=0,fixed=0.17.0; k8s.io/kubernetes (Go) SEMVER:introduced=0,fixed=1.16.0-beta.1.
Is there a fix for CVE-2019-11250?
Yes. k8s.io/client-go (Go): upgrade to 0.17.0 or later; k8s.io/kubernetes (Go): upgrade to 1.16.0-beta.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-11250?
Check whether you run k8s.io/client-go (Go) or k8s.io/kubernetes (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • k8s.io/client-go (Go): upgrade to 0.17.0 or later
    go get k8s.io/client-go@v0.17.0
  • k8s.io/kubernetes (Go): upgrade to 1.16.0-beta.1 or later
    go get k8s.io/kubernetes@v1.16.0-beta.1

Affected products

  • k8s.io/client-go (Go) SEMVER:introduced=0,fixed=0.17.0
  • k8s.io/kubernetes (Go) SEMVER:introduced=0,fixed=1.16.0-beta.1

Identifiers

  • CVE-2019-11250
  • GHSA-jmrx-5g74-6v2f
  • GO-2021-0065

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.