GHSA-VXG3-W9RV-RHR2

This is the same vulnerability as https://github.com/edgelesssys/contrast/security/advisories/GHSA-h5f8-crrq-4pw8. The original vulnerability had been fixed for release v1.8.1, but the fix was not ported to the main branch and thus not present in releases v1.9.0 ff.

Below is a brief repetition of the relevant sections from the first GHSA, where you can find the full details.

Workarounds

Existing workload secrets are compromised. The Contrast cluster needs to be newly initialized, and logging needs to be turned off.

References

First occurrence:

• https://github.com/edgelesssys/contrast/security/advisories/GHSA-h5f8-crrq-4pw8

We are defining a process for handling GHSAs that should prevent such regressions in the future:

• https://github.com/edgelesssys/contrast/pull/1739

• Workload secrets are visible to Kubernetes users with get or list permission on pods/logs, and thus need to be considered compromised.
• Since workload secrets are used for encrypted storage and Vault integration, those need to be considered compromised, too.

GHSA-VXG3-W9RV-RHR2 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.12.2); upgrading removes the vulnerable code path.

Kodem intelligence

Patches:

• https://github.com/edgelesssys/contrast/commit/5a5512c4af63c17bb66331e7bd2768a863b2f225
• https://github.com/edgelesssys/contrast/commit/cf58026b30c43fe7df91eac5322da02e1725d554

The patches are released with v1.12.2 and v1.13.0 (not yet published). Since the secrets are compromised, Contrast needs to be initialized from scratch.

1. What is GHSA-VXG3-W9RV-RHR2? GHSA-VXG3-W9RV-RHR2 is a high-severity security vulnerability in github.com/edgelesssys/contrast (go), affecting versions >= 1.9.0, <= 1.12.1. It is fixed in 1.12.2.
2. How severe is GHSA-VXG3-W9RV-RHR2? GHSA-VXG3-W9RV-RHR2 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-VXG3-W9RV-RHR2? github.com/edgelesssys/contrast (go) versions >= 1.9.0, <= 1.12.1 is affected.
4. Is there a fix for GHSA-VXG3-W9RV-RHR2? Yes. GHSA-VXG3-W9RV-RHR2 is fixed in 1.12.2. Upgrade to this version or later.
5. Is GHSA-VXG3-W9RV-RHR2 exploitable, and should I be worried? Whether GHSA-VXG3-W9RV-RHR2 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-VXG3-W9RV-RHR2 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-VXG3-W9RV-RHR2? Upgrade github.com/edgelesssys/contrast to 1.12.2 or later.