CVE-2020-8563: GO-2024-2755 - Sensitive Information leak for VSphere users via Log File in k8s.io/kubernetes

CVE-2020-8563 · Severity: low · CVSS 3.1 · Published 2024-06-05

Sensitive Information leak for VSphere users via Log File in k8s.io/kubernetes

Technologies: github.com/kubernetes/kubernetes (Go), k8s.io/kubernetes (Go). Vendors: Go.

Quick answers

Is CVE-2020-8563 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-8563 being exploited in the wild.
How severe is CVE-2020-8563?
Low severity, with a CVSS score of 3.1, published 5 June 2024.
Which products and versions are affected?
github.com/kubernetes/kubernetes (Go) SEMVER:introduced=0,fixed=1.19.3; k8s.io/kubernetes (Go) SEMVER:introduced=0,fixed=1.19.3.
Is there a fix for CVE-2020-8563?
Yes. github.com/kubernetes/kubernetes (Go): upgrade to 1.19.3 or later; k8s.io/kubernetes (Go): upgrade to 1.19.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-8563?
Check whether you run github.com/kubernetes/kubernetes (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

  • github.com/kubernetes/kubernetes (Go): upgrade to 1.19.3 or later
    go get github.com/kubernetes/kubernetes@v1.19.3
  • k8s.io/kubernetes (Go): upgrade to 1.19.3 or later
    go get k8s.io/kubernetes@v1.19.3

Affected products

  • github.com/kubernetes/kubernetes (Go) SEMVER:introduced=0,fixed=1.19.3
  • k8s.io/kubernetes (Go) SEMVER:introduced=0,fixed=1.19.3

Identifiers

  • CVE-2020-8563
  • GHSA-5xfg-wv98-264m
  • GO-2024-2755

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