Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik |
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik |
|
| No fix yet |
Traefik is an open source HTTP reverse proxy and load balancer. From 2.8.2 until 2.11.56 and 3.7.12, HTTP/3 entrypoints do not apply entryPoints..transport.respondingTimeouts.readTimeout because the timeout is enforced on a TCP connection and the HTTP/3 server has no corresponding QUIC stream deadline. An unauthenticated client can use a slow request body, trickling data indefinitely while holding a request and an upstream connection open and exhausting backends with bounded connection pools. This issue is fixed in 2.11.56 and 3.7.12.
From the CVE record · GitHub_M
Traefik HTTP/3 entrypoints do not enforce the configured read timeout on request bodies. An unauthenticated network client can trickle a request body indefinitely, holding a request and upstream connection open and potentially exhausting backends with bounded connection pools; no user interaction is required.
Check deployments using Go github.com/traefik/traefik/v2 versions >=2.8.2 and <2.11.56, github.com/traefik/traefik/v3 versions >=3.0.0 and <3.7.12, or any version of github.com/traefik/traefik.