Skip to content

@mittwald/kubernetes's secret contents leaked via debug logging

Moderate severity GitHub Reviewed Published May 2, 2023 in mittwald/node-kubernetes • Updated May 2, 2023

Package

npm @mittwald/kubernetes (npm)

Affected versions

< 3.5.0

Patched versions

3.5.0

Description

Impact

When debug logging is enabled (via DEBUG environment variable), the Kubernetes client may log all response bodies into the debug log -- including sensitive data from Secret resources.

When running in a Kubernetes cluster, this might expose sensitive information to users who are not authorised to access secrets, but have access to Pod logs (either directly using kubectl, or by Pod logs being shipped elsewhere).

Patches

Upgrade to 3.5.0 or newer.

Workarounds

Disable debug logging entirely, or exclude the kubernetes:client debug item (for example, using DEBUG=*,-kubernetes:client).

References

References

@martin-helmich martin-helmich published to mittwald/node-kubernetes May 2, 2023
Published to the GitHub Advisory Database May 2, 2023
Reviewed May 2, 2023
Last updated May 2, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-g35x-j6jj-8g7j

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.