Open redirect in Traefik
containous traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
|
containous traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
|
| github.com/containous/traefik Go |
|
|
| github.com/containous/traefik/v2 Go |
|
|
| github.com/traefik/traefik/api Go |
|
|
| github.com/traefik/traefik/v2/pkg/api Go |
|
|
| github.com/containous/traefik/api Go |
|
|
| github.com/containous/traefik/v2/pkg/api Go |
|
|
In Traefik before versions 1.7.26, 2.2.8, and 2.3.0-rc3, there exists a potential open redirect vulnerability in Traefik's handling of the "X-Forwarded-Prefix" header. The Traefik API dashboard component doesn't validate that the value of the header "X-Forwarded-Prefix" is a site relative path and will redirect to any header provided URI. Successful exploitation of an open redirect can be used to entice victims to disclose sensitive information. Active Exploitation of this issue is unlikely as it would require active header injection, however the Traefik team addressed this issue nonetheless to prevent abuse in e.g. cache poisoning scenarios.
From the CVE record · GitHub_M
The Traefik API dashboard does not validate that the X-Forwarded-Prefix header contains a site-relative path, allowing it to redirect to a URI supplied in that header. Exploitation requires active header injection; an attacker could use the redirect to entice a victim to disclose sensitive information.
Teams running affected Traefik Go packages should check versions before 1.7.26, affected 2.2.x versions before 2.2.8, and affected 2.3.0 release candidates before their package's listed fix.