GHSA-8WMP-HW5P-V2J7
GPUStack cluster proxy authorizes paths before dot segment normalization
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 2.3.0 | gpustack · -3 d desde divulgación | |
| Divulgación | Publicada | GHSA-8WMP-HW5P-V2J7 divulgada · CVSS 7.7 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
A path normalization mismatch in GPUStack's Kubernetes API proxy allows an authenticated user with access to a Kubernetes-provider cluster to bypass namespace and resource restrictions on read requests.
The server authorizes one representation of the request path, while downstream URL handling can interpret it as a different Kubernetes API path. The resulting request is sent using the worker's Kubernetes ServiceAccount credentials.
Exploitation requirements
Exploitation requires:
- An authenticated user with access to the target Kubernetes-provider cluster who is subject to the proxy's workload scope restrictions.
- A reachable worker capable of forwarding requests to the Kubernetes API server.
- A request path that reaches the vulnerable proxy in a form that passes its scope check but is interpreted differently during forwarding.
Cluster usage grants, including an Everyone grant where configured, may provide the required cluster access. Platform administrator or Organization Owner privileges are not required.
This issue does not require a deployment with multiple organizations. Reachability depends on how the deployment's ingress and HTTP components handle encoded paths.
Details
For restricted callers, the cluster proxy checks that the requested path refers to the permitted workload API and the caller's principal namespace.
In affected versions, this check occurs before all downstream path decoding and normalization. A crafted path can therefore pass the scope check but resolve to a resource outside the permitted namespace or API resource scope.
The worker forwards the resulting request using its Kubernetes ServiceAccount credentials without reapplying the original caller's scope restrictions.
Impact
An attacker may read Kubernetes resources outside their authorized scope, subject to the worker ServiceAccount's permissions. This can include sensitive resources such as Secrets when the ServiceAccount is permitted to read them.
The generated Kubernetes deployment manifests in v2.2.2 and v2.2.3 bind the worker ServiceAccount to `cluster-admin`. Other installation methods or customized RBAC configurations may grant different permissions.
The restricted caller path permits GET, HEAD, and OPTIONS requests and strips upgrade headers. This advisory does not establish a bypass of the method restrictions or direct access to mutation or exec operations.
Affected versions and patches
The vulnerable scope check is present in v2.2.2 and v2.2.3. The complete affected version range is specified in this advisory's package metadata.
The issue is fixed in v2.3.0. The server validates and canonicalizes the proxy path before authorization and forwards the same representation that was checked. Ambiguous encodings and traversal-shaped paths are rejected. The worker also validates paths as a defense-in-depth measure.
Upgrade the GPUStack server and workers to v2.3.0 or another release containing the fix.
Workarounds
Until an upgrade is possible, restrict access to the cluster proxy to trusted administrators or block the proxy endpoint at an access-control layer covering all server entry points. Blocking it may disrupt features that depend on the proxy.
Restrict cluster usage grants to trusted users and limit worker ServiceAccount permissions to those required for operation. These measures reduce exposure but do not correct the path authorization mismatch.
Ingress path normalization alone should not be treated as a complete mitigation.
Validation scope
The submitted reproduction used local server and worker routers, a synthetic Kubernetes response service, and test fixtures for caller identity and cluster access. It demonstrated forwarding outside the authorized namespace without reading real Kubernetes secrets.
Encoded-path behavior was tested through a modeled ingress normalization layer, not an actual shipped Higress deployment. End-to-end exploitability through the default gateway has not been established by that reproduction.
Related advisory
This issue bypasses workload scope restrictions introduced as part of the fix for GHSA-3hch-x692-6qj3 / CVE-2026-103002.
Credits
Reported by Syed Ghaffar of Opsbreak Inc.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pypigpustack |
Corregida | 2.3.0 | -3 d | 2.3.1 no afectada |
2.3.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/gpustack/gpustack/security/advisories/GHSA-8wmp-hw5p-v2j7Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
