Traefik allows path traversal using url encoding
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik Go |
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/traefik/traefik Go |
|
| No fix yet |
Traefik (pronounced traffic) is an HTTP reverse proxy and load balancer. Prior to versions 2.11.25 and 3.4.1, there is a potential vulnerability in Traefik managing the requests using a PathPrefix, Path or PathRegex matcher. When Traefik is configured to route the requests to a backend using a matcher based on the path, if the URL contains a URL encoded string in its path, it’s possible to target a backend, exposed using another router, by-passing the middlewares chain. This issue has been patched in versions 2.11.25 and 3.4.1.
From the CVE record · GitHub_M
Traefik routers using a PathPrefix, Path, or PathRegex matcher can mishandle requests whose URL path contains an encoded string. A request can reach a backend exposed through another router, bypassing its middleware chain. The input does not specify whether authentication or user interaction is required.
Operators using Traefik v3 before 3.4.1, v2 before 2.11.25, or any v1 version should check their path-based routing configurations.