Traefik HTTP/3 Backend NTLM Connection Reuse
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik |
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik |
|
| No fix yet |
Traefik is an open source HTTP reverse proxy and load balancer. From 2.11.0 until 2.11.57 and 3.7.13, the HTTP/3 entrypoint ConnContext does not call service.AddTransportOnContext, so kerberosRoundTripper uses a shared backend transport instead of a transport dedicated to each frontend connection. With HTTP/3 enabled, a backend using connection-bound NTLM or Negotiate authentication, and backend keep-alive, an unrelated client can reuse a backend connection authenticated for a victim, read victim-only data, and act as that victim without the victim credentials. This issue is fixed in 2.11.57 and 3.7.13.
From the CVE record · GitHub_M
Traefik’s HTTP/3 entrypoint can reuse a backend connection authenticated for another client. When HTTP/3 is enabled and a backend uses connection-bound NTLM or Negotiate authentication with keep-alive, an unrelated client can read victim-only data and act as the victim without the victim’s credentials.
Check deployments using github.com/traefik/traefik/v3 versions >=3.0.0 and <3.7.13, github.com/traefik/traefik/v2 versions >=2.11.0 and <2.11.57, or any version of github.com/traefik/traefik.