GHSA-gwhp-pf74-vj37 Fastify's connection header abuse enables stripping of proxy-added headers
Summary`@fastify/reply-from` and `@fastify/http-proxy` process the client's `Connection` header after the proxy has added its own headers via `rewriteRequestHeaders`. This allows attackers to retroactively strip proxy-added headers (like access control or identification headers) from upstream requests by listing them in the `Connection` header value. This affects applications using these plugins with custom header injection for routing, access control, or security purposes.DetailsThe vulnerability exists in `@fastify/reply-from/lib/request.js` at lines 128-136 (HTTP/1.1 handler) and lines 191-200 (undici handler). The processing flow is:Client headers are copied including the `connection` header (`@fastify/reply-from/index.js` line 91)The proxy adds custom headers via `rewriteRequestHeaders` (line 151)During request construction, the transport handlers read the client's `Connection` header and strip any headers listed in itThis stripping happens after `rewriteRequestHeaders`, allowing clients to target proxy-added headers for removalRFC 7230 Section 6.1 Connection header processing is intended for proxies to strip hop-by-hop headers from incoming requests before adding their own headers. The current implementation reverses this order, processing the client's Connection header after the proxy has already modified the header set.The call chain:`@fastify/reply-from/index.js` line 91: `headers = { ...req.headers }` — copies ALL client headers including `connection``index.js` line 151: `requestHeaders = rewriteRequestHeaders(this.request, headers)` — proxy adds custom headers (e.g., `x-forwarded-by`)`index.js` line 180: `requestImpl({...headers: requestHeaders...})` — passes headers to transport`request.js` line 191 (undici): `getConnectionHeaders(req.headers)` — reads Connection header FROM THE CLIENT`request.js` lines 198-200: Strips headers listed in Connection — including proxy-added headersThis is distinct from the general hop-by-hop forwarding concern — it's specifically about the client controlling which headers get stripped from the upstream request via the Connection header, subverting the proxy's `rewriteRequestHeaders` function.PoCSelf-contained reproduction with an upstream echo service and a proxy that adds a custom header:Actual output:The `x-forwarded-by` header that the proxy explicitly added in `rewriteRequestHeaders` is stripped before reaching the upstream.Multiple headers can be stripped at once by sending `Connection: x-forwarded-by, x-forwarded-for`.Both the undici (default) and HTTP/1.1 transport handlers in `@fastify/reply-from` are affected, as well as `@fastify/http-proxy` which delegates to `@fastify/reply-from`.ImpactAttackers can selectively remove any header added by the proxy's `rewriteRequestHeaders` function. This enables several attack scenarios:**Bypass proxy identification**: Strip headers that identify requests as coming through the proxy, potentially bypassing upstream controls that differentiate between direct and proxied requests**Circumvent access control**: If the proxy adds headers used for routing, authorization, or security decisions (e.g., `x-internal-auth`, `x-proxy-token`), attackers can strip them to access unauthorized resources**Remove arbitrary headers**: Any header can be targeted, including `Connection: authorization` to strip authentication or `Connection: x-forwarded-for, x-forwarded-by` to remove multiple headers at onceThis vulnerability affects deployments where the proxy adds security-relevant headers that downstream services rely on for access control decisions. It undermines the security model where proxies act as trusted intermediaries adding authentication or routing signals.Affected Versions`@fastify/reply-from` — All versions, both undici (default) and HTTP/1.1 transport handlers`@fastify/http-proxy` — All versions (delegates to `@fastify/reply-from`)Any configuration using `rewriteRequestHeaders` to add headers that could be security-relevantNo special configuration required to exploit — works with default settingsSuggested FixThe Connection header from the client should be processed and consumed before `rewriteRequestHeaders` is called, not after. Alternatively, the Connection header processing in `request.js` should maintain a list of headers that existed in the original client request and only strip those, not headers added by `rewriteRequestHeaders`.
CVSS v4.0 score: 9
CVSS v3.1 score: 8.6