GHSA-FF8Q-W4M5-4H73
create_cluster binds an arbitrary tenant's cloud credential with no ownership check
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-FF8Q-W4M5-4H73 divulgada · CVSS 6.4 (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's cloud cluster creation API allows an organization owner to bind another organization's cloud credential to a cluster they control.
The API accepts a caller-supplied `credential_id` without verifying that the credential is accessible to the caller or belongs to the cluster's organization. The background provisioning controller subsequently retrieves and uses that credential without checking the ownership relationship.
An attacker can therefore cause GPUStack to perform cloud provisioning operations using another organization's cloud account.
Affected configurations
Exploitation requires:
- An authenticated organization owner with permission to create cloud clusters and worker pools.
- A cloud credential belonging to another organization, with permissions sufficient for the requested provider operations.
- Knowledge or discovery of the credential's numeric ID.
Ordinary organization members and users limited to personal scope do not have the required cluster-creation permission. Deployments without organization owners managing separate cloud credentials do not meet the prerequisite for this cross-organization attack.
Impact
By creating a cluster referencing another organization's cloud credential and configuring a worker pool, an attacker can cause GPUStack to provision cloud instances in the account associated with that credential.
This can incur unauthorized charges and consume cloud resource quotas. GPUStack can also delete instances managed through the attacker's cluster using the same credential.
The impact is limited by the cloud credential's provider permissions and the operations exposed through GPUStack's provisioning workflow. This issue does not directly return the credential's secret value to the attacker, and unrestricted access to the victim's existing cloud resources has not been established.
Affected versions
GPUStack versions >= 2.2.0 and < 2.3.1.
Patches
GPUStack 2.3.1 validates cloud credential bindings when creating or updating a cluster. The credential must be accessible to the caller, belong to the same organization as the cluster, match the cluster's provider, and not be deleted.
The provisioning controller also revalidates persisted bindings before provisioning or deleting cloud instances. This prevents existing unauthorized bindings from continuing to reach provider APIs.
Cloud credential ownership and provider identity are immutable, while secret rotation remains supported.
Workarounds
Until upgrading, restrict cloud cluster creation and worker-pool provisioning to trusted administrators.
Review existing clusters for credential bindings whose ownership does not match the cluster's ownership. Restricting new cluster creation alone does not prevent background operations through an existing unauthorized binding.
Where an unauthorized binding is suspected, revoke or disable the associated credential at the cloud provider to prevent further use.
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-ff8q-w4m5-4h73Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
