Traefik: BasicAuth middleware: timing side-channel vulnerability
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
2.11.43| github.com/traefik/traefik Go |
| No fix yet |
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a timing side-channel vulnerability in Traefik's BasicAuth middleware that allows an attacker to enumerate valid usernames through response-time differences. The variable intended to hold a constant-time fallback secret always resolves to an empty string, causing the constant-time comparison to short-circuit in microseconds rather than performing a full bcrypt evaluation. This restores the original timing oracle and makes it possible to distinguish existing users from non-existing ones by measuring authentication response times. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.
From the CVE record · GitHub_M
Traefik’s BasicAuth middleware has a timing side channel that lets an attacker distinguish valid usernames by measuring authentication response times. An attacker can do this through HTTP authentication requests without prior authentication or user interaction.
Check deployments using affected versions of Go packages github.com/traefik/traefik/v3 (>=3.0.0-beta1 <3.6.14 or >=3.7.0-ea.1 <3.7.0-rc.2), github.com/traefik/traefik/v2 (<2.11.43), or github.com/traefik/traefik (all versions).