Traefik entrypoint header-name sanitization bypassed via request trailers
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik Go |
| No fix yet |
| github.com/traefik/traefik/v2 Go |
|
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik Go |
| No fix yet |
| github.com/traefik/traefik/v2 Go |
|
| No fix yet |
Traefik is an open source HTTP reverse proxy and load balancer. From 3.2.0 until 3.7.13, Traefik entrypoint defenses aliasHeadersStrategy, underscoreHeadersStrategy, and forwardedHeaders inspect req.Header but not req.Trailer, allowing an unauthenticated client to submit an aliasing or trusted header name in an HTTP/1.1 chunked trailer or an HTTP/2 trailer. When the retry or buffering middleware reads the body before the reverse proxy clones the request, the attacker-controlled trailer value reaches a backend that merges trailers into the header namespace, bypassing the documented delete or reject behavior and potentially spoofing identity or forwarded routing data. This issue is fixed in 3.7.13.
From the CVE record · GitHub_M
Traefik entrypoint defenses inspect request headers but not trailers. An unauthenticated network client can submit a crafted HTTP/1.1 or HTTP/2 trailer that may reach a backend and spoof identity or forwarded routing data when retry or buffering middleware reads the body before proxying and the backend merges trailers into headers. No user interaction is required.
Operators of Traefik 3.2.0 through versions before 3.7.13, or users of the Go packages github.com/traefik/traefik and github.com/traefik/traefik/v2, should check their deployments.