GHSA-vqv5-385r-2hf8: Contrast's unauthenticated recovery allows Coordinator impersonation
Impact Recovering coordinators do not verify the seed provided by the recovering party. This allows an attacker to set up a coordinator with a manifest that passes validation, but with a secret seed controlled by the attacker.
Published Feb 5, 2025 · Updated Feb 6, 2025
Affected packages
github.com/edgelesssys/contrast
- Ecosystem
- Go
- Affected
- <= 1.4.0
- Fixed in
- 1.4.1
- Check
go list -m github.com/edgelesssys/contrast
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Recovering coordinators do not verify the seed provided by the recovering party. This allows an attacker to set up a coordinator with a manifest that passes validation, but with a secret seed controlled by the attacker.
If network traffic is redirected from the legitimate coordinator to the attacker's coordinator, a workload owner is susceptible to impersonation if either
- they
seta new manifest and don't compare the root CA cert with the existing one (this is the default of thecontrastCLI) or - they
verifythe coordinator and don't compare the root CA cert with a trusted reference.
Under these circumstances, the attacker can:
- Issue certificates that chain back to the attacker coordinator's root CA.
- Recover arbitrary workload secrets of workloads deployed after the attack.
This issue does not affect the following:
- secrets of the legitimate coordinator (seed, workload secrets, CA)
- integrity of workloads, even when used with the rogue coordinator
- certificates chaining back to the mesh CA
Patches
This issue is patched in Contrast v1.4.1.
Workarounds
The issue can be avoided by verifying the coordinator root CA cert against expectations.
- At the first
setcall, keep a copy of the CA cert returned by the coordinator. - After subsequent
setorverifycalls, compare the returned CA cert with the backup copy. If it matches bit-for-bit, the coordinator is legitimate.
Credited to 3u13r, burgerdev, katexochen.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-3ccm-4qq2-5wrp
Constrata's coordinator transit engine `ciphertextContainer.UnmarshalJSON` panics on attacker-controlled short ciphertexts
medium4.3Jul 1, 2026GHSA-6c87-g9pw-78fx
Contrast's Imagepuller registryFor uses unanchored suffix matching, leaking auth credentials and trusted CA configuration to sibling-domain registries
low3.7Jul 1, 2026GHSA-rh99-wc69-c255
Contras Affected by CopyFile Policy Subversion via Symlinks
high8.1Apr 30, 2026GHSA-g9ww-x58f-9g6m
Contrast BadAML injection allows arbitrary code execution
high8.4Mar 26, 2026GHSA-f5p4-p5q5-jv3h
Contrast has insecure LUKS2 persistent storage partitions may be opened and used
medium5.7Oct 28, 2025GHSA-vxg3-w9rv-rhr2
Contrast leaks workload secrets to logs on INFO level
high7.3Aug 28, 2025
