Traefik's ACME TLS-ALPN fast path lacks timeouts and close on handshake stall
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 |
|
| No fix yet |
Traefik is an HTTP reverse proxy and load balancer. Prior to 2.11.35 and 3.6.7, there is a potential vulnerability in Traefik ACME TLS certificates' automatic generation: the ACME TLS-ALPN fast path can allow unauthenticated clients to tie up go routines and file descriptors indefinitely when the ACME TLS challenge is enabled. A malicious client can open many connections, send a minimal ClientHello with acme-tls/1, then stop responding, leading to denial of service of the entry point. The vulnerability is fixed in 2.11.35 and 3.6.7.
From the CVE record · GitHub_M
When the ACME TLS challenge is enabled, Traefik’s ACME TLS-ALPN fast path can let unauthenticated network clients tie up goroutines and file descriptors indefinitely. An attacker can open many connections and stop responding after a minimal ClientHello, causing denial of service at the entry point; no user interaction is required.
Operators of Traefik before 2.11.35 or 3.6.7, and users of the Go package github.com/traefik/traefik at any version, should check their deployments.