github.com/edgelesssys/contrast
Affected
- introduced
0, fixed1.8.1(semver)
Fixed versions
1.8.1
Fix
- Fixed version
1.8.1go get github.com/edgelesssys/[email protected]
Advisory
Also known as: CVE-2025-71425, GO-2025-3718
Contrast workload secrets leak to logs on INFO level
Impact
When the Contrast initializer is configured with a CONTRAST_LOG_LEVEL of info or debug, the workload secret is logged to stderr and written to Kubernetes logs.
Since info is the default setting, this affects all Contrast installations that don't customize their initializers' log level.
The following audiences are intended to have access to workload secrets (see https://docs.edgeless.systems/contrast/1.7/architecture/secrets#workload-secrets):
This vulnerability allows the following parties unintended access to workload secrets issued by a Coordinator:
get or list permission on pods/logs.This vulnerability does not affect scenarios where workload secrets are not used by the application (directly or with secure persistence). Applications designed for workload owner exclusion can't use workload secrets and are thus unaffected.
Patches
N/A
Workarounds
This vulnerability can be mitigated by adding an environment variable CONTRAST_LOG_LEVEL=warn to the initializer after running contrast generate, and then running contrast generate again.
References
N/A
High Basis: The source's own band: HIGH
0, fixed 1.8.1 (semver)1.8.1
1.8.1go get github.com/edgelesssys/[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