GHSA-w7wm-2425-7p2h: MarbleRun unauthenticated recovery allows Coordinator impersonation
(updated )
During recovery, a Coordinator only verifies that a given recovery key decrypts the sealed state, not if this key was provided by a party with access to one of the recovery keys defined in the manifest. This allows an attacker to manually craft a sealed state using their own recovery keys, and a manifest that does not match the rest of the state.
If network traffic is redirected from the legitimate coordinator to the attacker’s Coordinator, a remote party is susceptible to impersonation if they verify the Coordinator without comparing the root certificate of the Coordinator against a trusted reference.
Under these circumstances, an attacker can trick a remote party into trusting the malicious Coordinator by presenting a manifest that does not match the actual state of the deployment.
This issue does not affect the following:
- secrets and state of the legitimate Coordinator instances
- integrity of workloads
- certificates chaining back to the legitimate Coordinator root certificate
References
- github.com/advisories/GHSA-w7wm-2425-7p2h
- github.com/edgelesssys/marblerun
- github.com/edgelesssys/marblerun/commit/e4864f9f1d0f12a4a7d28514da43bcc75603a5b5
- github.com/edgelesssys/marblerun/releases/tag/v1.7.0
- github.com/edgelesssys/marblerun/security/advisories/GHSA-w7wm-2425-7p2h
- pkg.go.dev/vuln/GO-2025-3450
Detect and mitigate GHSA-w7wm-2425-7p2h with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →