Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-vqv5-385r-2hf8

HighCVSS 7.1 / 10
Published Feb 5, 2025·Last modified Feb 6, 2025
Affected Components(0)

No affected components available

Description

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 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
  • they verify the 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 set call, keep a copy of the CA cert returned by the coordinator.
  • 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.
Risk Scores
Base Score
7.1

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information. There is a high impact on the integrity of the data.

Threat Intelligence
6.5

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

High severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard