GHSA-FVJQ-6M4V-MW3M
Path-scoped middleware bypass on Fastify via absolute-form request targets with a query before the path
Texto original en inglés · Ver en español
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 11.2.9 | @nestjs/platform-fastify · -3 d desde divulgación | |
| Remediación | Parche 12.4.1 | @nestjs/platform-fastify · -3 d desde divulgación | |
| Divulgación | Publicada | GHSA-FVJQ-6M4V-MW3M divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
| Field | Value |
| --- | --- |
| Ecosystem | npm |
| Package | `@nestjs/platform-fastify` |
| Affected versions | `< 11.2.9` and `>= 12.0.0, < 12.4.1` |
| Patched versions | `11.2.9` and `12.4.1` |
| Severity | High |
| CVSS v3.1 | `AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N` (8.1) |
| CWE | CWE-436 (Interpretation Conflict), CWE-288 (Authentication Bypass Using an Alternate Path or Channel) |
Summary
On the Fastify adapter, a request whose absolute-form request target places a query string between the authority and
the path could reach a route handler without running the path-scoped Nest middleware bound to that route. Applications
that enforce authentication or authorization in middleware could run the protected handler with those checks skipped.
This completes the fix for GHSA-9c5c-9qcx-q35q https://github.com/nestjs/nest/security/advisories/GHSA-9c5c-9qcx-q35q.
Impact
An application is affected if it uses `@nestjs/platform-fastify`, binds middleware to specific paths with
`MiddlewareConsumer.forRoutes(...)` or `.exclude(...)`, and is reachable by clients that control the raw request line.
- 11.x: affected with the dependencies 11.2.x installs by default.
- 12.x: a default install is not affected, because the router bundled with current `fastify` versions resolves such
A reverse proxy that rewrites request targets to origin-form before they reach the application prevents the issue.
Details
The adapter and the router derived the path of such a target in different ways, so the middleware was matched against
a different path than the one the router dispatched to.
Patches
Fixed in 11.2.9 and 12.4.1. The adapter now derives the path the same way current router versions do, and a
target it can't resolve unambiguously is answered with 404 on every router version.
Workarounds
- Forward only origin-form request targets to the application, for example through a reverse proxy.
- On 12.x, use `fastify` 5.12.8 or later.
- Enforce authentication and authorization in guards, which run for the matched route, rather than in middleware.
Credit
Reported by Salih Caglar Ispirli.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npm@nestjs/platform-fastify |
Corregida | 11.2.9, 12.4.1 | -3 d · -3 d | 12.5.0 no afectada |
11.2.912.4.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/nestjs/nest/security/advisories/GHSA-fvjq-6m4v-mw3mLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
