Traefik Vulnerable to BasicAuth/DigestAuth Identity Spoofing via Non-Canonical headerField
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
3.7.0-ea.3| github.com/traefik/traefik Go |
| No fix yet |
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.42, 3.6.11, and 3.7.0-ea.3, when `headerField` is configured with a non-canonical HTTP header name (e.g., `x-auth-user` instead of `X-Auth-User`), an authenticated attacker can inject their own canonical version of that header to impersonate any identity to the backend. The backend receives two header entries — the attacker-injected canonical one is read first, overriding Traefik's non-canonical write. Versions 2.11.42, 3.6.11, and 3.7.0-ea.3 patch the issue.
From the CVE record · GitHub_M
Traefik is vulnerable when `headerField` is configured with a non-canonical HTTP header name. An authenticated attacker can supply the canonical version of that header, causing the backend to read the attacker’s value first and potentially impersonate another identity.
Teams running Go packages github.com/traefik/traefik/v2 before 2.11.42, github.com/traefik/traefik/v3 in the listed affected ranges, or github.com/traefik/traefik at any version should check their deployments.