GHSA-4766-X535-JW3R

Vulnerability from github – Published: 2025-11-04 18:39 – Updated: 2025-11-17 21:38
VLAI?
Summary
kgateway is missing xDS authorization
Details

Summary

The xDS interface in Kgateway versions 2.0.0 through 2.0.4 lacks authentication, allowing any client with unrestricted network access to the xDS port to retrieve potentially sensitive configuration data including certificate data, backend service information, routing rules, and cluster metadata.

Description

Impact

Kgateway xDS interface did not have authorization, so anonymous clients with unrestricted network access could gain access to the xDS data. This could expose sensitive information about your gateway configuration, certificate data, backend services, and routing topology to unauthorized parties.

Patches

Upgrade to version 2.0.5 or 2.1.0. These versions enable JWT-based authentication for the xDS interface by default, ensuring that only authenticated clients can access the xDS configuration data.

Workarounds

If immediate upgrade is not possible, NetworkPolicies can be used to block access to kgateway's xDS port, restricting network access to only trusted sources.

References

  • Fix in 2.1.0: https://github.com/kgateway-dev/kgateway/pull/12471
  • Backport to 2.0.5: https://github.com/kgateway-dev/kgateway/pull/12535
  • Related issue: https://github.com/kgateway-dev/kgateway/issues/10651

Credits

Kindly reported by @rikatz

For More Information

If you have any questions or comments about this advisory, please reach out in slack https://cloud-native.slack.com/archives/C080D3PJMS4

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/kgateway-dev/kgateway/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.1.0-agw-cel-rbac"
            },
            {
              "fixed": "2.1.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/kgateway-dev/kgateway/v2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-64323"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-11-04T18:39:31Z",
    "nvd_published_at": "2025-11-07T04:15:47Z",
    "severity": "MODERATE"
  },
  "details": "## Summary\n\nThe xDS interface in Kgateway versions 2.0.0 through 2.0.4 lacks authentication, allowing any client with unrestricted network access to the xDS port to retrieve potentially sensitive configuration data including certificate data, backend service information, routing rules, and cluster metadata.\n\n## Description\n\n### Impact\n\nKgateway xDS interface did not have authorization, so anonymous clients with unrestricted network access could gain access to the xDS data. This could expose sensitive information about your gateway configuration, certificate data, backend services, and routing topology to unauthorized parties.\n\n### Patches\n\nUpgrade to version 2.0.5 or 2.1.0. These versions enable JWT-based authentication for the xDS interface by default, ensuring that only authenticated clients can access the xDS configuration data.\n\n### Workarounds\n\nIf immediate upgrade is not possible, NetworkPolicies can be used to block access to kgateway\u0027s xDS port, restricting network access to only trusted sources.\n\n## References\n\n- Fix in 2.1.0: https://github.com/kgateway-dev/kgateway/pull/12471\n- Backport to 2.0.5: https://github.com/kgateway-dev/kgateway/pull/12535\n- Related issue: https://github.com/kgateway-dev/kgateway/issues/10651\n\n## Credits\n\nKindly reported by @rikatz\n\n## For More Information\n\nIf you have any questions or comments about this advisory, please reach out in slack https://cloud-native.slack.com/archives/C080D3PJMS4",
  "id": "GHSA-4766-x535-jw3r",
  "modified": "2025-11-17T21:38:28Z",
  "published": "2025-11-04T18:39:31Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/kgateway-dev/kgateway/security/advisories/GHSA-4766-x535-jw3r"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-64323"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kgateway-dev/kgateway/issues/10651"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kgateway-dev/kgateway/pull/12471"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kgateway-dev/kgateway/pull/12535"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/kgateway-dev/kgateway"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "kgateway is missing xDS authorization"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…