CVE-2019-11251: GO-2022-0802 - Kubernetes kubectl cp Vulnerable to Symlink Attack in k8s.io/kubernetes

CVE-2019-11251 · Severity: low · CVSS 3.1 · Published 2024-08-21

Kubernetes kubectl cp Vulnerable to Symlink Attack in k8s.io/kubernetes

Technologies: k8s.io/kubernetes (Go). Vendors: Go.

Quick answers

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

Affected products

  • k8s.io/kubernetes (Go) SEMVER:introduced=1.13.10,fixed=1.13.11, SEMVER:introduced=1.13.10,fixed=1.13.11,introduced=1.14.6,fixed=1.14.7,introduced=1.15.3,fixed=1.16.0

Identifiers

  • CVE-2019-11251
  • GHSA-6qfg-8799-r575
  • GO-2022-0802

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