Skip to content
Fencer Intel
critical 9.1

GHSA-x5r5-2qrx-rqj8 json

Transparent TLS may not be applied to Marbles with certain manifest configurations

published 2y ago modified 2y ago also GO-2024-2583

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

Summary

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

Patch / fix

  • go github.com/edgelesssys/marblerun 1.4.1

Is GHSA-x5r5-2qrx-rqj8 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

CVSS scores

assigned by version score vector
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

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

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.