CVE-2019-1002101: GO-2022-0782 - Symlink Attack in kubectl cp in k8s.io/kubernetes

CVE-2019-1002101 · Severity: low · CVSS 3 · Published 2024-08-21

Symlink Attack in kubectl cp in k8s.io/kubernetes

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

Quick answers

Is CVE-2019-1002101 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-1002101 being exploited in the wild.
How severe is CVE-2019-1002101?
Low severity, with a CVSS score of 3, published 21 August 2024.
Which products and versions are affected?
k8s.io/kubernetes (Go) SEMVER:introduced=0,fixed=1.11.9, SEMVER:introduced=0,fixed=1.11.9,introduced=1.12.0,fixed=1.12.7,introduced=1.13.0,fixed=1.13.5.
Is there a fix for CVE-2019-1002101?
Yes. k8s.io/kubernetes (Go): upgrade to 1.11.9, 1.13.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-1002101?
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.11.9, 1.13.5 or later
    go get k8s.io/kubernetes@v1.13.5

Affected products

  • k8s.io/kubernetes (Go) SEMVER:introduced=0,fixed=1.11.9, SEMVER:introduced=0,fixed=1.11.9,introduced=1.12.0,fixed=1.12.7,introduced=1.13.0,fixed=1.13.5

Identifiers

  • CVE-2019-1002101
  • GHSA-34jx-wx69-9x8v
  • GO-2022-0782

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