Disclosed weakness · no CVE recorded

GPUStack provider cloning could disclose another organization’s token

GPUStack · GPUStack

First documented disclosure · Review checkpoint

Summary

Under the conditions described by GPUStack, cloning another organization’s model provider could reveal its stored upstream access token.

Severity and exploitation evidence

Medium · 4.4/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

Cloning a model provider did not verify ownership of the source credential.

Conditions required

An organization owner knows the source provider identity and the identifying hash of the stored token.

Potential impact

A provider credential could be exposed and used against the upstream service within its scope.

Affected versions and configurations

>= 2.2.0, < 2.3.0

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. Review cloned providers and rotate potentially exposed upstream tokens.

Operating lesson

A matching token identifier does not confer the right to copy the underlying secret.

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