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.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Traefik | Traefik | * | 2.10.5 (including) |
| Traefik | Traefik | 3.0.0-beta1 (including) | 3.0.0-beta1 (including) |
| Traefik | Traefik | 3.0.0-beta2 (including) | 3.0.0-beta2 (including) |
| Traefik | Traefik | 3.0.0-beta3 (including) | 3.0.0-beta3 (including) |
| Traefik | Traefik | 3.0.0-beta4 (including) | 3.0.0-beta4 (including) |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.