NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

Transparent TLS may not be applied to Marbles with certain manifest configurationsGHSA-x5r5-2qrx-rqj8

CRITICALFix: edgelesssys/marblerun@0330ced

GHSA-x5r5-2qrx-rqj8 is a critical-severity (CVSS 9.1) 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-2024-2583
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Mar 4, 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

Transparent TLS (TTLS) is a MarbleRun feature that wraps plain TCP connections between Marbles in TLS. In the manifest, a user defines the connections that should be considered.

Impact

If a Marble is configured for TTLS, but doesn't have an environment variable defined in its parameters, TTLS is not applied. The traffic will not be encrypted.

MarbleRun deployments that don't use TTLS (which is only available with EGo Marbles) are not affected.

Patches

The issue has been patched in v1.4.1.

Workarounds

Make sure that all Marbles that use TTLS have an environment variable defined in their parameters.

References

For a description of TTLS, see https://docs.edgeless.systems/marblerun/features/transparent-TLS See the updated section on TTLS configuration in the manifest: https://docs.edgeless.systems/marblerun/workflows/define-manifest#tls

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/edgelesssys/marblerunall versions1.4.1go get github.com/edgelesssys/marblerun@v1.4.1

Detection & mitigation playbook

Open-source dependency

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

  2. Fix

    Update github.com/edgelesssys/marblerun to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x5r5-2qrx-rqj8 is resolved across your whole dependency graph.

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

Transparent TLS (TTLS) is a MarbleRun feature that wraps plain TCP connections between Marbles in TLS. In the manifest, a user defines the connections that should be considered. ### Impact If a Marble is configured for TTLS, but doesn't have an environment variable defined in its parameters, TTLS is not applied. The traffic will not be encrypted. MarbleRun deployments that don't use TTLS (which is only available with EGo Marbles) are not affected. ### Patches The issue has been patched in [`v1.4.1`](https://github.com/edgelesssys/marblerun/releases/tag/v1.4.1). ### Workarounds Make sure th
O3 Security · Impact-Aware SCA

Is GHSA-x5r5-2qrx-rqj8 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Transparent TLS may not be applied to Marbles with…