Uncontrolled Resource Consumption in Traefik
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 open source HTTP reverse proxy and load balancer. The traefik docker container uses 100% CPU when it serves as its own backend, which is an automatically generated route resulting from the Docker integration in the default configuration. This issue has been addressed in versions 2.10.6 and 3.0.0-beta5. Users are advised to upgrade. There are no known workarounds for this vulnerability.
From the CVE record · GitHub_M
In the default Docker integration configuration, Traefik can generate a route that makes it its own backend. Serving that route can drive the Traefik container to 100% CPU; authentication and user-interaction requirements are not specified.
Check deployments using Go package github.com/traefik/traefik/v2 before 2.10.6, github.com/traefik/traefik/v3 before 3.0.0-beta5, or any version of github.com/traefik/traefik.