GHSA-X5R5-2QRX-RQJ8

Vulnerability from github – Published: 2024-02-27 19:02 – Updated: 2024-02-27 19:02
VLAI
Summary
Transparent TLS may not be applied to Marbles with certain manifest configurations
Details

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

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/edgelesssys/marblerun"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.4.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": true,
    "github_reviewed_at": "2024-02-27T19:02:15Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "details": "Transparent TLS (TTLS) is a MarbleRun feature that wraps plain TCP connections between Marbles in TLS.\nIn the manifest, a user defines the connections that should be considered.\n\n### Impact\nIf a Marble is configured for TTLS, but doesn\u0027t have an environment variable defined in its parameters, TTLS is not applied.\nThe traffic will not be encrypted.\n\nMarbleRun deployments that don\u0027t use TTLS (which is only available with EGo Marbles) are not affected.\n\n### Patches\nThe issue has been patched in [`v1.4.1`](https://github.com/edgelesssys/marblerun/releases/tag/v1.4.1).\n\n### Workarounds\nMake sure that all Marbles that use TTLS have an environment variable defined in their parameters.\n\n### References\nFor a description of TTLS, see \u003chttps://docs.edgeless.systems/marblerun/features/transparent-TLS\u003e\nSee the updated section on TTLS configuration in the manifest: \u003chttps://docs.edgeless.systems/marblerun/workflows/define-manifest#tls\u003e \n",
  "id": "GHSA-x5r5-2qrx-rqj8",
  "modified": "2024-02-27T19:02:15Z",
  "published": "2024-02-27T19:02:15Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/edgelesssys/marblerun/security/advisories/GHSA-x5r5-2qrx-rqj8"
    },
    {
      "type": "WEB",
      "url": "https://github.com/edgelesssys/marblerun/commit/0330ced092253613a07abe7b330ff6ac6fc6e9c6"
    },
    {
      "type": "WEB",
      "url": "https://github.com/edgelesssys/marblerun/commit/e5bcfe32883d22f3d87ffc9400f9fdb5ecbe3200"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/edgelesssys/marblerun"
    },
    {
      "type": "WEB",
      "url": "https://github.com/edgelesssys/marblerun/releases/tag/v1.4.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Transparent TLS may not be applied to Marbles with certain manifest configurations"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.