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
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| npm | @mittwald/kubernetes | < 3.5.0 | 3.5.0 | GHSA-g35x-j6jj-8g7j |
References
- https://github.com/mittwald/node-kubernetes/security/advisories/GHSA-g35x-j6jj-8g7j web
- https://github.com/mittwald/node-kubernetes/commit/04f6809fd438417c343d541e57f76f0040e069cd web
- https://github.com/mittwald/node-kubernetes package
- https://github.com/mittwald/node-kubernetes/releases/tag/v3.5.0 web