Incorrect processing of fragment in the URL leads to Authorization Bypass 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. When a request is sent to Traefik with a URL fragment, Traefik automatically URL encodes and forwards the fragment to the backend server. This violates RFC 7230 because in the origin-form the URL should only contain the absolute path and the query. When this is combined with another frontend proxy like Nginx, it can be used to bypass frontend proxy URI-based access control restrictions. This vulnerability 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
Traefik URL-encodes fragments in incoming requests and forwards them to backend servers. When Traefik is used with another frontend proxy such as Nginx, an attacker can use this behavior to bypass URI-based access controls on that proxy. The input does not specify authentication or user-interaction requirements.
Check deployments using Go github.com/traefik/traefik/v2 before 2.10.6, github.com/traefik/traefik/v3 before 3.0.0-beta5, or github.com/traefik/traefik at any version.