HTTP client can remove the X-Forwarded headers in Traefik
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik Go |
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik Go |
|
|
Traefik is a golang, Cloud Native Application Proxy. When a HTTP request is processed by Traefik, certain HTTP headers such as X-Forwarded-Host or X-Forwarded-Port are added by Traefik before the request is routed to the application. For a HTTP client, it should not be possible to remove or modify these headers. Since the application trusts the value of these headers, security implications might arise, if they can be modified. For HTTP/1.1, however, it was found that some of theses custom headers can indeed be removed and in certain cases manipulated. The attack relies on the HTTP/1.1 behavior, that headers can be defined as hop-by-hop via the HTTP Connection header. This issue has been addressed in release versions 2.11.9 and 3.1.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.
From the CVE record · GitHub_M
Traefik can allow an HTTP client to remove or, in some cases, manipulate headers it adds before routing an HTTP/1.1 request to an application. The attack uses the HTTP Connection header to mark headers as hop-by-hop; applications that trust the affected headers may face security implications.
Teams running Traefik or the affected Go packages should check versions before 2.11.9, and v3 versions from 3.0.0-beta3 through versions before 3.1.3.