Disclosed weakness · no CVE recorded

GPUStack proxy checks could expose Kubernetes data outside permitted scope

GPUStack · GPUStack

First documented disclosure · Review checkpoint

Summary

A cluster user could read Kubernetes resources outside the part of the cluster their role allowed them to inspect.

Severity and exploitation evidence

High · 7.7/10 · CVSS 3.1. Severity source.

Exploitation not established: The original source establishes the weakness but does not report malicious exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The Kubernetes proxy and its access checks interpreted the requested resource differently.

Conditions required

A signed-in user has access to a Kubernetes-backed GPUStack cluster.

Potential impact

Read requests could expose data outside the permitted namespace or resource scope.

Affected versions and configurations

>= 2.2.2, <= 2.2.3

Fix and mitigation status

2.3.0 fixes this issue.

Practical next steps

Upgrade to 2.3.0 or a later release containing this fix. Audit out-of-scope reads and restrict the worker’s Kubernetes read permissions.

Operating lesson

Evaluate authorization against the exact resource identity sent upstream.

Evidence and limits

GPUStack shipped 2.3.0 on October 23. GitHub records an edit to the release notes on October 26, when GPUStack published the dated advisory. No CVE was listed in the advisory at review.

Sources