GHSA-H5F8-CRRQ-4PW8

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

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):

• Contrast Coordinator (can derive all workload secrets)
• Contrast Initializer (obtains only the secret configured in the manifest)
• Seedshare owner (can derive all workload secrets)
• Workload owner (can update manifests to obtain secrets)

This vulnerability allows the following parties unintended access to workload secrets issued by a Coordinator:

• Kubernetes users with get or list permission on pods/logs.
• Others with read access to the Kubernetes log storage (most notably, the cloud provider).

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.

GHSA-H5F8-CRRQ-4PW8 has a CVSS score of 7.3 (High). The vector is reachable from an adjacent network, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-H5F8-CRRQ-4PW8? GHSA-H5F8-CRRQ-4PW8 is a high-severity security vulnerability in github.com/edgelesssys/contrast (go), affecting versions <= 1.8.0. It is fixed in 1.8.1.
2. How severe is GHSA-H5F8-CRRQ-4PW8? GHSA-H5F8-CRRQ-4PW8 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/edgelesssys/contrast are affected by GHSA-H5F8-CRRQ-4PW8? github.com/edgelesssys/contrast (go) versions <= 1.8.0 is affected.
4. Is there a fix for GHSA-H5F8-CRRQ-4PW8? Yes. GHSA-H5F8-CRRQ-4PW8 is fixed in 1.8.1. Upgrade to this version or later.
5. Is GHSA-H5F8-CRRQ-4PW8 exploitable, and should I be worried? Whether GHSA-H5F8-CRRQ-4PW8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-H5F8-CRRQ-4PW8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-H5F8-CRRQ-4PW8? Upgrade github.com/edgelesssys/contrast to 1.8.1 or later.