Description (CNA)
@fastify/reply-from v12.6.1 and earlier and @fastify/http-proxy v11.4.3 and earlier 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 from upstream requests by listing them in the Connection header value. Any header added by the proxy for routing, access control, or security purposes can be selectively removed by a client. @fastify/http-proxy is also affected as it delegates to @fastify/reply-from. Upgrade to @fastify/reply-from v12.6.2 or @fastify/http-proxy v11.4.4 or later.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| @fastify/reply-from / @fastify/reply-from | affected 0 before 12.6.2; unaffected 12.6.2 |
| @fastify/reply-from / @fastify/http-proxy | affected 0 before 11.4.4; unaffected 11.4.4 |
CWE
CWE-644
References
- https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-gwhp-pf74-vj37
- https://cna.openjsf.org/security-advisories.html
ADP enrichment
No English description supplied.
A flaw was found in @fastify/reply-from and @fastify/http-proxy. A remote attacker can exploit this vulnerability by manipulating the Connection header in client requests. This allows the attacker to remove specific headers that the proxy has added for security, routing, or access control purposes. Consequently, an attacker could bypass security mechanisms or gain unauthorized access to resources.