@fastify/http-proxy
@fastify/http-proxy vulnerable to prefix escape via backslash dot-segments
@fastify/http-proxy versions before 11.6.2 do not validate proxied HTTP request paths for backslash based dot-segments before forwarding them to the configured upstream. The plain HTTP request handler skips the destination validation that the WebSocket path performs, and the underlying reply-from library only rejects forward-slash traversal, so a request containing backslash dot-segments can escape the boundary set by the prefix and rewritePrefix options. An unauthenticated network attacker can use this to reach upstream paths that were meant to stay hidden behind the proxy, resulting in disclosure of internal endpoints. This is a path traversal issue (CWE-22). Users should upgrade to @fastify/http-proxy 11.6.2 or later.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 11.6.2
Fixed in 11.6.2
Mitigation
Upgrade @fastify/http-proxy to 11.6.2 or later.
References
- Vendor advisory github.com/fastify/fastify-http-proxy/security…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.