@mittwald/kubernetes
Affected
- introduced
0, fixed3.5.0(semver)
Fixed versions
3.5.0
Fix
- Fixed version
3.5.0npm install @mittwald/[email protected]
Advisory
Also known as: None
@mittwald/kubernetes's secret contents leaked via debug logging
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
Medium Basis: The source's own band: MODERATE
0, fixed 3.5.0 (semver)3.5.0
3.5.0npm install @mittwald/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0