GHSA-MJ6Q-MP44-53V8
Share scopes do not follow user renames
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-MJ6Q-MP44-53V8 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Remediación | Parche 5.5.2 | jupyterhub · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
Sharing permissions do not properly follow user renames, which can lead to improperly applied permissions if a user is renamed and a subsequent user is later created with the earlier user's name while a share has been granted.
Only affects deployments with user-initiated sharing enabled, and requires user renames to take place (requires admin privileges) and requires a new user to be created with a previously renamed user's original name (typically not under user control).
Patches
Update to JupyterHub 5.5.2
Workarounds
Do not enable user-initiated sharing (not enabled by default) and/or rename users (rare, requires admin permissions).
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pypijupyterhub |
Corregida | 5.5.2 | 0 d | 6.2.0 no afectada |
5.5.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-mj6q-mp44-53v8Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
