CVE-2019-11244: Kubernetes Unsafe Cacheing

CVE-2019-11244 · Severity: low · CVSS 3.1 · Published 2022-02-15

Kubernetes Unsafe Cacheing

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

Quick answers

Is CVE-2019-11244 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-11244 being exploited in the wild.
How severe is CVE-2019-11244?
Low severity, with a CVSS score of 3.1, published 15 February 2022.
Which products and versions are affected?
k8s.io/client-go (Go) SEMVER:introduced=1.8.0,fixed=1.12.9.
Is there a fix for CVE-2019-11244?
Yes. k8s.io/client-go (Go): upgrade to 1.12.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-11244?
Check whether you run k8s.io/client-go (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 1.12.9 or later
    go get k8s.io/client-go@v1.12.9

Affected products

  • k8s.io/client-go (Go) SEMVER:introduced=1.8.0,fixed=1.12.9

Identifiers

  • CVE-2019-11244
  • GHSA-2575-pghm-6qqx

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