Traefik has a possible vulnerability with the path matchers
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 (pronounced traffic) is an HTTP reverse proxy and load balancer. In versions prior to 2.11.24, 3.3.6, and 3.4.0-rc2. 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 /../ 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.24, 3.3.6, and 3.4.0-rc2. A workaround involves adding a `PathRegexp` rule to the matcher to prevent matching a route with a `/../` in the path.
From the CVE record · GitHub_M
Traefik is vulnerable when a router uses a PathPrefix, Path, or PathRegex matcher to route requests to a backend. A request containing `/../` in its URL path can reach a backend exposed through another router and bypass its middleware chain. The description does not specify authentication or user-interaction requirements.
Check deployments using Go packages github.com/traefik/traefik/v2 before 2.11.23, github.com/traefik/traefik/v3 before 3.3.6 or from 3.4.0-rc1 to before 3.4.0-rc2, or github.com/traefik/traefik at any listed version.