Drop Headers via Malicious Connection Header
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik Go |
| No fix yet |
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik Go |
| No fix yet |
Traefik is an HTTP reverse proxy and load balancer. Prior to version 2.4.13, there exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse. If one has a chain of Traefik middlewares, and one of them sets a request header, then sending a request with a certain Connection header will cause it to be removed before the request is sent. In this case, the backend does not see the request header. A patch is available in version 2.4.13. There are no known workarounds aside from upgrading.
From the CVE record · GitHub_M
Traefik can remove a request header set by a middleware before forwarding the request to the backend if a requester sends a crafted Connection header. Privilege escalation is possible only if a chain of middlewares sets that header and the backend's failure to receive it would allow elevated privileges.
Check deployments using Go package github.com/traefik/traefik/v2 before 2.4.13 or github.com/traefik/traefik at version 1.7.30 or earlier.