Summary When trustProxy is configured with a restrictive trust function (e.g., a specific IP like trustProxy: '10.0.0.1', a subnet, a hop count, or a custom function), the request.protocol and request.host getters read X-Forwarded-Proto and X-Forwarded-Host headers from any connection — including connections from untrusted IPs. This allows an attacker connecting directly to Fastify (bypassing the proxy) to spoof both the protocol and host seen by the application. Affected Versions fastify <= 5.8.2 Impact Applications using request.protocol or request.host for security decisions (HTTPS enforcement, secure cookie flags, CSRF origin checks, URL construction, host-based routing) are affected when trustProxy is configured with a restrictive trust function. When trustProxy: true (trust everything), both host and protocol trust all forwarded headers — this is expected behavior. The vulnerability only manifests with restrictive trust configurations.
oryginał ENCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:NFastify
APPFastify< 5.8.3
Powiązane podatności
Impact: Fastify applications using schema.body.content for per-content-type body validation can have validati...
Fastify is a fast and low overhead web framework, for Node.js. Prior to version 5.7.2, a validation bypass vul...
Fastify is a fast and low overhead web framework, for Node.js. In versions 5.0.0 to 5.3.0 as well as version 4...
fastify is a fast and low overhead web framework, for Node.js. Affected versions of fastify are subject to a d...
Fastify node module before 0.38.0 is vulnerable to a denial-of-service attack by sending a request with "Conte...