Loading HuntDB...

CVE-2020-8565

MEDIUM
Published 2020-12-07T22:00:19.374983Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2020-8565. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
4.7
/10
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.001
probability
of exploitation in the wild

There is a 0.1% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.185
Higher than 18.5% of all CVEs

Attack Vector Metrics

Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED

Impact Metrics

Confidentiality
HIGH
Integrity
NONE
Availability
NONE

Description

In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects <= v1.19.3, <= v1.18.10, <= v1.17.13, < v1.20.0-alpha2.

Understanding This Vulnerability

This Common Vulnerabilities and Exposures (CVE) entry provides detailed information about a security vulnerability that has been publicly disclosed. CVEs are standardized identifiers assigned by MITRE Corporation to track and catalog security vulnerabilities across software and hardware products.

The severity rating (MEDIUM) indicates the potential impact of this vulnerability based on the CVSS (Common Vulnerability Scoring System) framework. Higher severity ratings typically indicate vulnerabilities that could lead to more significant security breaches if exploited. Security teams should prioritize remediation efforts based on severity, exploit availability, and the EPSS (Exploit Prediction Scoring System) score, which predicts the likelihood of exploitation in the wild.

If this vulnerability affects products or systems in your infrastructure, we recommend reviewing the affected products section, checking for available patches or updates from vendors, and implementing recommended workarounds or solutions until a permanent fix is available. Organizations should also monitor security advisories and threat intelligence feeds for updates about active exploitation of this vulnerability.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

References

Workarounds

Do not enable verbose logging in production (log level >= 9), limit access to logs.

Credits & Acknowledgments

Patrick Rhomberg (purelyapplied)

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed MODERATE

Kubernetes client-go vulnerable to Sensitive Information Leak via Log File

GHSA-8cfg-vx93-jvxw

Advisory Details

In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects <= v1.19.5, <= v1.18.13, <= v1.17.15, < v1.20.0-alpha2.

Affected Packages

Go k8s.io/client-go
ECOSYSTEM: ≥0.19.0 <0.19.6
Go k8s.io/client-go
ECOSYSTEM: ≥0.20.0-alpha.0 <0.20.0-alpha.2
Go k8s.io/client-go
ECOSYSTEM: ≥0.18.0 <0.18.14
Go k8s.io/client-go
ECOSYSTEM: ≥0 <0.17.16
Go k8s.io/kubernetes
ECOSYSTEM: ≥0 <1.20.0-alpha.2

CVSS Scoring

CVSS Score

5.0

CVSS Vector

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

Advisory provided by GitHub Security Advisory Database. Published: February 6, 2023, Modified: May 20, 2024

References

Published: 2020-12-07T22:00:19.374983Z
Last Modified: 2024-09-17T00:05:58.669Z
Copied to clipboard!