GHSA-vqv5-385r-2hf8: Github.com/edgelesssys/contrast Contrast's Unauthenticated Recovery Allows Coordinator Vulnerability
HIGHGHSA-vqv5-385r-2hf8 is a HIGH (CVSS 7.1) contrast's unauthenticated recovery allows coordinator vulnerability (CWE-285: Improper Authorization) affecting Github.com/edgelesssys/contrast libraries in the Go ecosystem. The issue involves contrast's unauthenticated recovery allows coordinator impersonation. Remediation is available by upgrading affected packages to version 1.4.1.
GHSA-vqv5-385r-2hf8 at a Glance
Security Impact
CVSS: 7.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N).
How to Fix GHSA-vqv5-385r-2hf8
To remediate this vulnerability, upgrade all affected Github.com/edgelesssys/contrast dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/edgelesssys/contrast to 1.4.1Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/edgelesssys/contrastHow to Check if You Are Affected
To determine whether your application is affected by GHSA-vqv5-385r-2hf8, inspect your project dependencies for Github.com/edgelesssys/contrast:
inspect dependencies for github.com/edgelesssys/contrastAnalyze the terminal output to locate any version of Github.com/edgelesssys/contrast in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.4.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In Github.com/edgelesssys/contrast, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-vqv5-385r-2hf8 Affected Github.com/edgelesssys/contrast Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/edgelesssys/contrast
|
Go |
< 1.4.1
|
1.4.1
|
References
Frequently Asked Questions
What is GHSA-vqv5-385r-2hf8?
Which Github.com/edgelesssys/contrast versions are affected?
What version fixes GHSA-vqv5-385r-2hf8?
Is github.com/edgelesssys/contrast affected?
What is the CVSS score of GHSA-vqv5-385r-2hf8?
What CWE is associated with GHSA-vqv5-385r-2hf8?
How can I check Go dependencies for GHSA-vqv5-385r-2hf8?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-vqv5-385r-2hf8",
"modified" : "2025-02-06T18:05:15Z",
"published" : "2025-02-05T21:30:35Z",
"aliases" : [ ],
"summary" : "Contrast's unauthenticated recovery allows Coordinator impersonation",
"details" : "### Impact\n\nRecovering 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. \n\nIf network traffic is redirected from the legitimate coordinator to the attacker's coordinator, a workload owner is susceptible to impersonation if either \n\n* they `set` a new manifest and don't compare the root CA cert with the existing one (this is the default of the `contrast` CLI) or\n* they `verify` the coordinator and don't compare the root CA cert with a trusted reference.\n\nUnder these circumstances, the attacker can:\n\n* Issue certificates that chain back to the attacker coordinator's root CA.\n* Recover arbitrary workload secrets of workloads deployed after the attack.\n\nThis issue does **not** affect the following:\n\n* secrets of the legitimate coordinator (seed, workload secrets, CA)\n* integrity of workloads, even when used with the rogue coordinator\n* certificates chaining back to the mesh CA\n\n### Patches\n\nThis issue is patched in Contrast v1.4.1.\n\n### Workarounds\n\nThe issue can be avoided by verifying the coordinator root CA cert against expectations.\n\n* At the first `set` call, keep a copy of the CA cert returned by the coordinator.\n* After subsequent `set` or `verify` calls, compare the returned CA cert with the backup copy. If it matches bit-for-bit, the coordinator is legitimate.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/edgelesssys/contrast"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.4.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.4.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/edgelesssys/contrast/security/advisories/GHSA-vqv5-385r-2hf8"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/edgelesssys/contrast"
}, {
"type" : "WEB",
"url" : "https://pkg.go.dev/vuln/GO-2025-3455"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-285" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-02-05T21:30:35Z",
"nvd_published_at" : null
}
}