GHSA-2R75-Q53F-V8PX
Case-insensitive comparison of invite, email-change, MFA and other security tokens
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-2R75-Q53F-V8PX divulgada · CVSS 7.4 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
Several authentication-critical tokens were stored in MySQL columns using the case-insensitive `utf8mb4_unicode_ci` collation and looked up with a plain `=` comparison. Any case-mutation of a valid token was therefore accepted as the original. Affected tokens included invite acceptance (`invites.token`), email-change confirmation (`email_changes.token`), local MFA (`local_mfa.token`), session keys (`sessions.key`), device authentication tokens (`host_device_auth.token`), and the Apple ADE enrollment profile token. An earlier fix (Fleet 4.89.0) had hardened only the password reset token.
Impact
An attacker who obtained a case-normalized copy of a token (for example from case-folding mail clients, proxy or server logs, OCR of a screenshot, or manual transcription) could use it as if it were the original. The highest-impact path is account takeover through the email-change flow: confirming a victim's email change with a case-mutated token redirects the account's email to the attacker, who then completes a password reset. An invite token could likewise be redeemed with the invited role, up to Global Admin. Case-insensitive matching collapses roughly 2^26 case variants of a 32-character token into a single accepted value, reducing effective entropy accordingly.
Patches
Fixed in Fleet 4.92.0 (fleetdm/fleet#51471). Migration `20260825213833_TokenColumnsCaseSensitive` moves the affected token columns to the byte-exact `utf8mb4_bin` collation, and a schema test prevents new token columns from being added without an explicit case-sensitive collation.
Workarounds
None. Upgrade to Fleet 4.92.0 or later.
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 @deepak9347 for responsibly reporting this issue through our Vulnerability Disclosure Program https://bugbop.com/programs/b5f2f20e-fe4d-466b-a474-6db65b4d2bb3.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/fleetdm/fleet/v4 |
Sin parche | — | — | v4.43.4 afectada |
4.92.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-2r75-q53f-v8pxLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
