Skip to content

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

Critical severity GitHub Reviewed Published Feb 27, 2024 in edgelesssys/marblerun • Updated Feb 27, 2024

Package

gomod github.com/edgelesssys/marblerun (Go)

Affected versions

< 1.4.1

Patched versions

1.4.1

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

References

@daniel-weisse daniel-weisse published to edgelesssys/marblerun Feb 27, 2024
Published to the GitHub Advisory Database Feb 27, 2024
Reviewed Feb 27, 2024
Last updated Feb 27, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-x5r5-2qrx-rqj8

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.