Skip to content

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

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

Medium Go
Severity
6.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.54%
Chance of exploitation in the next 30 days. Higher than 45.42% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-532 Insertion of Sensitive Information into Log File
Fix
Available
2 packages have a fixed version

Description

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

Affected versions

Go

PackageVulnerableFixed in
github.com/kubernetes/kubernetes
< 1.19.3
1.19.3
k8s.io/kubernetes
< 1.19.3
1.19.3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/kubernetes/kubernetes Go → 1.19.3

go
go get github.com/kubernetes/kubernetes@v1.19.3 && go mod tidy

k8s.io/kubernetes Go → 1.19.3

go
go get k8s.io/kubernetes@v1.19.3 && go mod tidy

Severity breakdown

CVSS 3.1 6.3

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it
  • Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Distribution: Remove debug log files before deploying the application into production.
  • Operation: Protect log files against unauthorized read/write.
  • Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-r6j8-c6r2-37rr
kube-controller-manager is vulnerable to half-blind Server Side Request Forgery through in-tree Portworx StorageClass
Medium Also affects k8s.io/kubernetes
GHSA-4x4m-3c2p-qppc
Kubernetes Nodes can delete themselves by adding an OwnerReference
Medium Also affects k8s.io/kubernetes
GHSA-hj2p-8wj8-pfq4
kubernetes allows nodes to bypass dynamic resource allocation authorization checks
Low Also affects k8s.io/kubernetes
GO-2025-3547
Kubernetes kube-apiserver Vulnerable to Race Condition
Low Also affects k8s.io/kubernetes
GHSA-3wgm-2gw2-vh5m
Kubernetes GitRepo Volume Inadvertent Local Repository Access
Medium Also affects k8s.io/kubernetes
GHSA-vv39-3w5q-974q
Kubernetes allows Command Injection affecting Windows nodes via nodes/*/logs/query API
Medium Also affects k8s.io/kubernetes
GHSA-jgfp-53c3-624w
Node Denial of Service via kubelet Checkpoint API
Medium Also affects k8s.io/kubernetes
GHSA-27wf-5967-98gx
Kubernetes kubelet arbitrary command execution
High Also affects k8s.io/kubernetes
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor