GHSA-GV75-J3V8-3CRM
@better-auth/passkey: Passkey verification does not enforce origin or user verification
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 1.4.0 | better-auth · -346 d desde divulgación | |
| Divulgación | Publicada | GHSA-GV75-J3V8-3CRM divulgada · CVSS 3.1 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Remediación | Parche 1.7.16 | @better-auth/passkey · 0 d desde divulgación | |
| Remediación | Parche 1.8.0-beta.5 | @better-auth/passkey · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Am I affected?
You are affected if you use `@better-auth/passkey` 1.4.0-beta.16 or later, or the passkey plugin built into `better-auth` before 1.4.0, and any of these is true:
- You set `authenticatorSelection.userVerification` to `"required"`.
- Your relying party ID also covers origins you do not control, such as other subdomains.
Summary
User verification. With `userVerification: "required"`, the server asked the authenticator to verify the user, for example with a PIN or fingerprint, but did not confirm that it happened. The default `"preferred"` setting allows responses without this check by design.
Origin. The server took the expected WebAuthn origin from the request instead of from its configuration.
Impact
A user can register or use a passkey without the PIN or biometric check your application requires. A passkey response created on another origin under the same relying party ID could be accepted. Neither problem lets anyone register a passkey for another user's account or skip the sign-in needed to register one.
Patches
Upgrade `@better-auth/passkey` to 1.7.16, or to 1.8.0-beta.5 on the beta line.
The expected origin now comes from the `origin` option, or from the `baseURL` origin plus a frontend origin listed exactly in `trustedOrigins`. Set `origin` when `rpID` is set and a wildcard in `baseURL.allowedHosts` covers it. `userVerification` now also applies to authentication.
Workarounds
None verified beyond upgrading.
Technical details
The registration and authentication handlers passed the request's origin to WebAuthn verification and did not set the required user verification flag. They now use the configured origin and require the user verification flag when `userVerification` is `"required"`.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npm@better-auth/passkey |
Corregida | 1.7.16, 1.8.0-beta.5 | 0 d · 0 d | 1.7.25 no afectada |
npmbetter-auth |
Corregida | 1.4.0 | -346 d | 1.7.26 no afectada |
1.4.01.7.161.8.0-beta.5Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/better-auth/better-auth/security/advisories/GHSA-gv75-j3v8-3crmLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
