Skip to content
Fencer Intel
high —

GHSA-j3rq-4xjw-xg63 json

Go package github.com/edgelesssys/marblerun CLI commands susceptible to MITM attacks

published 2y ago modified 8mo ago also GO-2023-2378

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact Any CLI command issued to a Coordinator after the Manifest has been set, is susceptible to be redirected to another MarbleRun Coordinator instance, which runs the same binary, but potentially a different manifest.

### Patches The issue has been patched in [`v1.4.0`](https://github.com/edgelesssys/marblerun/releases/tag/v1.4.0)

### Workarounds

Directly using the REST API of the Coordinator and manually verifying and pinning the certificate to a set Manifest avoids the issue.

Patch / fix

  • go github.com/edgelesssys/marblerun 1.4.0

Is GHSA-j3rq-4xjw-xg63 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/edgelesssys/marblerun
<1.4.0
1.4.0

Classification

Weakness
  • CWE-300 Channel Accessible by Non-Endpoint

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.