ghsa-gf93-xccm-5g6j
Vulnerability from github
Published
2025-11-04 15:43
Modified
2025-11-06 15:30
Severity ?
8.7 (High) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Summary
MARIN3R: Cross-Namespace Vulnerability in the Operator
Details

Summary

Cross-namespace Secret access vulnerability in DiscoveryServiceCertificate allows users to bypass RBAC and access Secrets in unauthorized namespaces.

Affected Versions

All versions prior to v0.13.4

Patched Versions

v0.13.4 and later

Impact

Users with permission to create DiscoveryServiceCertificate resources in one namespace can indirectly read Secrets from other namespaces, completely bypassing Kubernetes RBAC security boundaries.

Workarounds

Restrict DiscoveryServiceCertificate create permissions to cluster administrators only until patched version is deployed.

Credit

Thanks to @debuggerchen for the responsible disclosure.

Show details on source website

To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.13.3"
      },
      "package": {
        "ecosystem": "Go",
        "name": "github.com/3scale-sre/marin3r"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.13.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-64171"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-11-04T15:43:52Z",
    "nvd_published_at": "2025-11-06T01:15:38Z",
    "severity": "HIGH"
  },
  "details": "## Summary\nCross-namespace Secret access vulnerability in DiscoveryServiceCertificate \nallows users to bypass RBAC and access Secrets in unauthorized namespaces.\n\n## Affected Versions\nAll versions prior to v0.13.4\n\n## Patched Versions\nv0.13.4 and later\n\n## Impact\nUsers with permission to create DiscoveryServiceCertificate resources in one \nnamespace can indirectly read Secrets from other namespaces, completely \nbypassing Kubernetes RBAC security boundaries.\n\n## Workarounds\nRestrict DiscoveryServiceCertificate create permissions to cluster administrators \nonly until patched version is deployed.\n\n## Credit\nThanks to @debuggerchen for the responsible disclosure.",
  "id": "GHSA-gf93-xccm-5g6j",
  "modified": "2025-11-06T15:30:15Z",
  "published": "2025-11-04T15:43:52Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/3scale-sre/marin3r/security/advisories/GHSA-gf93-xccm-5g6j"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-64171"
    },
    {
      "type": "WEB",
      "url": "https://github.com/3scale-sre/marin3r/pull/294"
    },
    {
      "type": "WEB",
      "url": "https://github.com/3scale-sre/marin3r/commit/859b14115fde1d67620e645cd1b62e90e30d9981"
    },
    {
      "type": "WEB",
      "url": "https://github.com/3scale-sre/marin3r/commit/c60246a43ae8c0c38dd7267f298d68a121a159fa"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/3scale-sre/marin3r"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "MARIN3R: Cross-Namespace Vulnerability in the Operator"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.