GHSA-MJ9P-FQ5H-MW8H
Team administrator can create or escalate users into teams they do not administer
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-MJ9P-FQ5H-MW8H divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
A broken access control vulnerability in Fleet's user administration API allows a team administrator to create user accounts with roles on teams they do not administer, including granting administrator access on those teams. This enables a malicious team administrator to gain control over other teams within the same Fleet instance.
Impact
Fleet scopes administrative permissions on a per-team basis. In affected versions, when a user was created (or modified) with membership across multiple teams, the authorization check was satisfied as long as the caller administered at least one of the target user's teams, rather than requiring authority over every team being assigned.
As a result, a team administrator could provision a user with administrator roles on other teams, including teams where the caller holds no role at all, and then use those credentials to act on those teams. Because Fleet team administrators can deploy software and execute scripts on enrolled hosts, this effectively allows a malicious administrator of one team to take over other teams and the devices they manage. In multi-tenant deployments where teams represent separate business units, departments, or customers, this breaks team isolation guarantees.
Exploitation requires authentication as a team administrator.
Patches
- v4.89.0
Workarounds
There is no workaround for this issue short of upgrading to a patched version. Until upgrading, organizations should restrict team administrator permissions to trusted users and review recently created or modified user accounts for unexpected team or role assignments.
For more information
If you have any questions or comments about this advisory:
Email us at [security@fleetdm.com](mailto:security@fleetdm.com)
Join #fleet in osquery Slack https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw
Credits
We thank Niclovin for responsibly reporting this issue through our Vulnerability Disclosure Program https://bugbop.com/programs/b5f2f20e-fe4d-466b-a474-6db65b4d2bb3.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Gogithub.com/fleetdm/fleet |
Corregida | 4.89.0 | — | — |
4.89.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/fleetdm/fleet/security/advisories/GHSA-mj9p-fq5h-mw8hLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
