CyberRota Analysis
AI-GeneratedVersions of @fastify/http-proxy prior to 11.6.2 are vulnerable to a path traversal issue that allows unauthenticated attackers to exploit backslash-based dot-segments in proxied HTTP request paths, potentially disclosing sensitive internal endpoints. This vulnerability arises from inadequate validation of request paths before forwarding them to upstream servers. Organizations utilizing affected versions should prioritize upgrading to version 11.6.2 or later to mitigate the risk of unauthorized access to internal resources.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
@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.
Related CVEs
Other vulnerabilities affecting the same vendor(s)