GPUStack missing authorization allows cross-user access and cluster takeover
First seen Nov 10 Updated Nov 10, 17:18 UTC Heat 54 high evidence
A GitHub advisory says GPUStack's cluster_apiserver_proxy handler skipped resource-level authorization checks. An authenticated non-admin user could reach clusters they are not allowed to use. Requests went out under a worker's Kubernetes ServiceAccount, so the impact depends on that account's permissions. It could include reading resources, changing workloads or running code in the cluster.
- What to do
- Upgrade gpustack to 2.2.2 and review the permissions of worker ServiceAccounts.
- Who should care
- Operators of multi-user GPUStack setups connected to Kubernetes clusters.
Key facts
- Affected
- gpustack (pip) >= 2.2.0, < 2.2.2
- Patched version
- 2.2.2
Context
The same 2.2.2 release also fixes the SAML authentication bypass.
Timeline
Official
Evidence
High evidence: the claim comes from an official source (the company or project itself), or at least two independent sites reported it.
Details written Nov 10, 17:17 UTC from the sources listed above.