GHSA-9VWX-HFM8-G59G
Cross-tenant cluster takeover and registration-token theft via SYSTEM-principal write-gate bypass
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-9VWX-HFM8-G59G divulgada · CVSS 8.8 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Remediación | Parche 2.3.1 | gpustack · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
An authorization flaw in GPUStack allows cluster and worker service credentials to perform infrastructure management operations beyond their intended scope.
Affected authorization checks treat SYSTEM principals as broadly trusted without consistently enforcing their assigned cluster or restricting them to required runtime operations.
An attacker holding a valid cluster registration token or worker service credential can therefore access management operations targeting resources outside the credential's intended scope, including retrieving another cluster's registration token.
Affected configurations
Exploitation requires a valid cluster registration token or worker service credential and network access to the management API.
An organization owner can obtain a registration token for a cluster they are authorized to manage. Possession of such a token is sufficient to reach the vulnerable authorization path; an ordinary user account alone is not.
The issue does not require multiple organizations. It can also affect deployments where credentials intended for one cluster are held by users or systems that should not manage other clusters.
Impact
An attacker can retrieve other clusters' registration tokens and perform unauthorized updates or deletions affecting clusters, worker pools, cloud credential records, and inference backend configurations.
These operations can compromise cluster registration, alter deployment behavior, and disrupt workloads or provisioning across the deployment.
Changes to custom inference backend images or commands may cause attacker-controlled code to run when a subsequent deployment uses the modified configuration. The resulting execution privileges depend on the worker and workload configuration.
The identified credential disclosure concerns cluster registration tokens. Public cloud credential responses do not directly return the stored cloud credential secret.
Affected versions
GPUStack versions >= 2.2.0 and < 2.3.1.
Patches
GPUStack 2.3.1 restricts ordinary cluster and worker service credentials to explicitly permitted runtime endpoints and HTTP methods.
Resource authorization derives the credential's scope from its authenticated cluster relationship and enforces the applicable cluster and ownership boundaries. Caller-supplied organization selection cannot widen that scope.
Ordinary service credentials can no longer use infrastructure management endpoints to retrieve registration tokens or modify organization-wide configuration. Permitted bootstrap and runtime operations remain subject to resource-level authorization.
Workarounds
Until upgrading, restrict management API access to trusted hosts and limit access to cluster registration tokens and worker service credentials.
These measures reduce exposure but do not correct the authorization flaw for callers that retain API access and a valid affected credential.
Additional remediation
Upgrading does not revoke credentials that may already have been exposed or undo unauthorized configuration changes.
Revoke and replace potentially compromised cluster registration tokens and worker service credentials. Review cluster settings, worker pools, cloud credential records, and custom inference backend definitions for unauthorized changes.
If modified backend configurations were used to launch workloads, review those workloads and any data or credentials available to them.
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.1 | 0 d | 2.3.1 no afectada |
2.3.1Arsenal 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-9vwx-hfm8-g59gLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
