Traefik: unbounded io.ReadAll on auth server response body causes OOM denial of service(DOS)
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik Go |
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik Go |
|
| No fix yet |
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.38 and 3.6.9, there is a potential vulnerability in Traefik managing the ForwardAuth middleware responses. When Traefik is configured to use the ForwardAuth middleware, the response body from the authentication server is read entirely into memory without any size limit. There is no maxResponseBodySize configuration to restrict the amount of data read from the authentication server response. If the authentication server returns an unexpectedly large or unbounded response body, Traefik will allocate unlimited memory, potentially causing an out-of-memory (OOM) condition that crashes the process. This results in a denial of service for all routes served by the affected Traefik instance. This issue has been patched in versions 2.11.38 and 3.6.9.
From the CVE record · GitHub_M
Traefik reads ForwardAuth authentication-server response bodies into memory without a size limit. When ForwardAuth is configured and the authentication server returns an unexpectedly large or unbounded body, Traefik can run out of memory and crash, denying service to all routes on that instance.
Check deployments using Go package github.com/traefik/traefik/v2 before 2.11.38, github.com/traefik/traefik/v3 before 3.6.9, or github.com/traefik/traefik at any version.