How severe is GHSA-j3rq-4xjw-xg63?

No CVSS score has been assigned to GHSA-j3rq-4xjw-xg63 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j3rq-4xjw-xg63?

GHSA-j3rq-4xjw-xg63 affects the following packages: github.com/edgelesssys/marblerun (Go). Ecosystems affected: Go.

How do I fix GHSA-j3rq-4xjw-xg63?

Update github.com/edgelesssys/marblerun to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3rq-4xjw-xg63 is resolved across your whole dependency graph.

How do I detect GHSA-j3rq-4xjw-xg63 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/edgelesssys/marblerun, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j3rq-4xjw-xg63 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-j3rq-4xjw-xg63 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j3rq-4xjw-xg63 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-j3rq-4xjw-xg63 published, and has it been updated?

GHSA-j3rq-4xjw-xg63 was published on December 4, 2023 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Go package github.com/edgelesssys/marblerun CLI commands susceptible to MITM attacksGHSA-j3rq-4xjw-xg63

GHSA-j3rq-4xjw-xg63 is a security vulnerability in github.com/edgelesssys/marblerun. A fix is available for github.com/edgelesssys/marblerun — see the affected versions and patch details below.

Also known asGO-2023-2378

Published

Dec 4, 2023

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 21, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/edgelesssys/marblerun

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

Workarounds

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/edgelesssys/marblerun`	all versions	1.4.0`go get github.com/edgelesssys/marblerun@v1.4.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/edgelesssys/marblerun, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/edgelesssys/marblerun to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3rq-4xjw-xg63 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-j3rq-4xjw-xg63 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

Go package github.com/edgelesssys/marblerun CLI commands susceptible to MITM attacksGHSA-j3rq-4xjw-xg63

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-j3rq-4xjw-xg63 in your dependencies?