GHSA-gvhc-wv3v-7pf8 Kite has an authenticated cluster RBAC bypass in /api/v1/overview
SummaryAuthenticated Kite users with any role can request `/api/v1/overview` for a cluster that their roles do not permit by selecting that cluster with `x-cluster-name`. The overview route is registered before `middleware.RBACMiddleware()` and `GetOverview` only checks `len(user.Roles) > 0`, so it returns aggregate Kubernetes inventory and capacity data from unauthorized clusters.The issue is present on current main commit `38c9bb9d4b746c0d2a8252f3c35cdfa07ab01c21` and latest release `v0.12.2` at commit `0aae35abb2d6a8adf623fe60349261aa48753ccc`.ImpactA low-privileged user who only has access to one cluster can set `x-cluster-name` to another configured cluster and retrieve aggregate inventory and resource sizing data for that cluster. The response includes total node, pod, namespace, service, CPU, and memory values. This bypasses the cluster membership boundary used elsewhere in Kite.The validated impact is confidentiality only. I did not prove Kubernetes mutation, pod names, secret values, kubeconfig contents, or bearer token exposure through this endpoint.Technical details`routes.go` registers `/api/v1/overview` before the global RBAC middleware is applied:`routes.go:131-133`: `/api/v1` gets `RequireAuth()` and `ClusterMiddleware(cm)`.`routes.go:135`: `/api/v1/overview` is registered.`routes.go:171`: `api.Use(middleware.RBACMiddleware())` is applied only after overview and several other routes are registered.`pkg/middleware/cluster.go:21-40` accepts the target cluster name from `x-cluster-name`, query, or cookie and injects the matching `ClientSet` without checking whether the user can access that cluster.`pkg/system/handler.go:47-52` retrieves the selected cluster and user, but only rejects users with zero roles:It then lists nodes, pods, namespaces, and services for the selected cluster at `pkg/system/handler.go:63-137` and returns aggregate data at `pkg/system/handler.go:147-169`.The intended cluster boundary exists elsewhere. `pkg/cluster/cluster_handler.go:19-47` filters `/api/v1/clusters` with `rbac.CanAccessCluster(user, name)`, and `pkg/rbac/rbac.go:32-40` implements that cluster check. The vulnerable overview path skips the same check.ReproductionConfigure Kite with at least two clusters, for example `dev-cluster` and `prod-cluster`.Create a user with a role that allows only `dev-cluster` and does not match `prod-cluster`.Authenticate as that user.Send `GET /api/v1/overview` with header `x-cluster-name: prod-cluster`.Observe that the response includes aggregate inventory and capacity data for `prod-cluster` instead of returning 403.I also validated this locally with a Go proof test. The test constructs a fake `prod-cluster` containing one node, namespace, service, and pod. The user has a role limited to `dev-cluster` and `dev-ns` only. Before calling the handler, both controls return false:`rbac.CanAccess(user, "pods", "get", "prod-cluster", "_all")``rbac.CanAccessCluster(user, "prod-cluster")`The direct handler call then succeeds and returns the unauthorized production cluster aggregate data.Command run:Key output:Suggested remediationAdd an explicit cluster and resource authorization check before any overview data is queried. At minimum, reject users without `rbac.CanAccessCluster(user, cs.Name)`. A stricter fix should require the same resource permissions used by the AI `get_cluster_overview` tool:`get nodes` at cluster scope`get pods` across all namespaces`get namespaces` at cluster scope`get services` across all namespacesAlso consider moving every route that lacks its own complete authorization below `api.Use(middleware.RBACMiddleware())`, or adding per-handler authorization tests for all pre-RBAC routes.
CVSS v3.1 score: 4.3