Impact: @fastify/http-proxy versions up to and including 11.5.0 fail to rewrite the request prefix when the prefix segment is URL-encoded. Fastify's router URL-decodes paths for route matching, but request.url retains the original encoded form, and the prefix-rewrite step uses a literal string replace against the decoded prefix. A request that encodes one or more characters of the configured prefix therefore matches the route but skips the rewrite, so the raw encoded path is forwarded to the upstream unchanged. The upstream then decodes the path and serves it, letting an attacker reach upstream paths that the proxy was configured to hide via rewritePrefix, including internal or administrative endpoints. Patches: upgrade to @fastify/http-proxy 11.6.0. Workarounds: none.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NFastify Fastify\/http Proxy
APPFastify< 11.6.0
Related vulnerabilities
Usuwanie nagłówków proxy przez manipulację nagłówkiem Connection w @fastify/reply-from
Path traversal w @fastify/http-proxy — ucieczka poza prefix WebSocket
Fastify/Middie: pominięcie middleware przez zakodowany slash w URL
Pominięcie middleware w @fastify/express — obejście uwierzytelniania
Pominięcie uwierzytelnienia w @fastify/middie — brak dziedziczenia middleware