GHSA-72J3-6RMW-742X
World-readable jwt_secret_key and cluster tokens in /var/lib/gpustack let a local user forge admin JWTs (authentication bypass)
Texto original en inglés · Ver en español
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 2.3.0 | gpustack · -3 d desde divulgación | |
| Divulgación | Publicada | GHSA-72J3-6RMW-742X divulgada · CVSS 8.5 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
GPUStack does not enforce restrictive permissions when creating certain credential files in affected versions.
On POSIX deployments using a permissive process umask, such as 022, these files can be readable by other local users who can traverse the data directory. The default POSIX data directory is `/var/lib/gpustack`; custom data directories can also be affected.
Disclosure of the JWT signing key actively used by the server allows an attacker to forge session tokens for existing users, including administrators.
Details
Affected credential-writing paths rely on ordinary file creation without explicitly enforcing owner-only permissions. With umask 022, newly created credential files typically receive mode 0644.
Affected files include the locally generated `jwt_secret_key`, registration and worker token files, and the generated `initial_admin_password` where present.
The actual exposure depends on file and directory permissions, filesystem ACLs, mounts, and deployment configuration. Deployments that already prevent other principals from reading these files are not exposed through this file-read path.
Exploitation requirements
The attacker must be able to access the relevant filesystem as a principal other than the intended credential owner and read an affected credential file.
A GPUStack account is not required. A co-located container is relevant only if it can access the affected files through its mounts or shared filesystem.
Administrator impersonation additionally requires the disclosed JWT key to be the key currently used by the GPUStack server and access to the server's authentication endpoints.
Impact
Disclosure of the active server JWT signing key permits impersonation of existing active users, including platform administrators.
Disclosure of a valid registration token may permit unauthorized worker registration. Disclosure of a worker token may permit impersonation of the corresponding worker, subject to the credential's scope.
A disclosed initial administrator password may permit administrator access if it remains valid.
Affected versions and patches
Affected versions: < 2.3.0
Fixed in 2.3.0.
The fix creates credential files with owner-only permissions and tightens permissions on existing credential files during startup where the filesystem permits it. The data directory retains traversal access needed by the embedded PostgreSQL service.
Upgrade to 2.3.0 or another release containing the fix.
Workarounds and recovery
Restrict affected credential files to their intended service account, using mode 0600 on POSIX systems, and prevent untrusted users or containers from accessing credential storage.
Preserve directory traversal required by services such as the embedded PostgreSQL instance. A restrictive umask alone does not repair permissions on existing files.
If exposure is suspected, rotate the server's active JWT signing key, revoke and replace affected registration and worker credentials, and change any exposed administrator password that remains valid.
JWT key rotation invalidates sessions signed with the old key. Review registered workers and account changes for unauthorized activity.
Permission changes and upgrades do not invalidate credentials that an attacker has already copied.
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.0 | -3 d | 2.3.1 no afectada |
2.3.0Arsenal 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-72j3-6rmw-742xLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
