@fastify/express versions 4.0.6 and earlier only rewrite the plugin prefix for middleware mount paths when the path argument is a string. Non-string mount paths (arrays of paths and regular expressions) are left unprefixed inside prefixed plugin scopes, so middleware registered with those forms does not match the actual prefixed request path. Applications that use path-scoped middleware for authentication, authorization, rate limiting, or auditing on routes inside a prefixed scope can be bypassed by sending a request to the prefixed route, because Fastify still matches the route but the middleware is skipped. Patches: upgrade to @fastify/express 4.0.7. Workarounds: use string mount paths instead of arrays or regular expressions in prefixed plugins, or register one use call per path.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NFastify Fastify\/express
APPFastify< 4.0.7
Powiązane podatności
Pominięcie middleware security w @fastify/express — bypass uwierzytelniania
Pominięcie uwierzytelnienia w @fastify/express via znormalizowane URL
@fastify/middie versions 9.1.0 through 9.3.2 decode the encoded slash %2F inside path parameter values before ...
Pominięcie uwierzytelnienia w @fastify/middie — brak dziedziczenia middleware
Usuwanie nagłówków proxy przez manipulację nagłówkiem Connection w @fastify/reply-from