Advisory

GHSA-g35x-j6jj-8g7j

Also known as: None

Summary

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

Details

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

  • https://cwe.mitre.org/data/definitions/532.html

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2023-05-02 16:51 UTC
Modified
2023-05-02 16:51 UTC

Affected packages and fixes

@mittwald/kubernetes

npm · All systems

Affected

  • introduced 0, fixed 3.5.0 (semver)

Fixed versions

3.5.0

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences