Traefik doesn't Prevent Path Normalization Bypass in Router + Middleware Rules
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik Go |
| No fix yet |
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik Go |
| No fix yet |
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik/v3 Go |
|
|
Traefik is an HTTP reverse proxy and load balancer. For versions prior to 2.11.32 and 2.11.31 through 3.6.2, requests using PathPrefix, Path or PathRegex matchers can bypass path normalization. When Traefik uses path-based routing, requests containing URL-encoded restricted characters (/, \, Null, ;, ?, #) can bypass the middleware chain and reach unintended backends. For example, a request to http://mydomain.example.com/admin%2F could reach service-a without triggering my-security-middleware, bypassing security controls for the /admin/ path. This issue is fixed in versions 2.11.32 and 3.6.3.
From the CVE record · GitHub_M
Traefik requests matched by PathPrefix, Path, or PathRegex can bypass path normalization. When path-based routing is used, a network attacker can send URL-encoded restricted characters to bypass the middleware chain and reach an unintended backend. The input does not specify an authentication requirement or user interaction.
Operators of github.com/traefik/traefik/v2 before 2.11.32, github.com/traefik/traefik/v3 before 3.6.3, or the affected github.com/traefik/traefik package should check their deployments.