# CVE-2019-11244: Kubernetes Unsafe Cacheing

Source: https://junglewise.ai/threats/cve-2019-11244-kubernetes-unsafe-cacheing  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-02-15  
License: CC BY 4.0 with a link back

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

Kubernetes Unsafe Cacheing

Technologies: [k8s.io/client-go (Go)](https://junglewise.ai/threats/technologies/k8s-io-client-go). Vendors: [Go](https://junglewise.ai/threats/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

  ```sh
  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

## Related threats

- [GO-2021-0065 - Unauthorized credential disclosure in k8s.io/kubernetes and k8s.io/client-go](https://junglewise.ai/threats/cve-2019-11250-kubernetes-client-go-library-logs-may-disclose-credentials-to)
- [GO-2021-0064 - Unauthorized credential disclosure via debug logs in k8s.io/kubernetes and k8s.io/client-go](https://junglewise.ai/threats/cve-2020-8565-kubernetes-client-go-vulnerable-to-sensitive-information-leak-via)