Open redirect in Traefik

Summary

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.

Timeline

1. Jul 30, 2020, 3:20 PM UTCCVE published
2. Aug 4, 2024, 1:08 PM UTCRecord last updated

Affected versions

• containous traefik

  fixed in 1.7.26; From 2.0.0 · fixed in 2.2.8

• github.com/traefik/traefikGo

  From 1.5.0-rc5 · fixed in 1.7.26

• github.com/traefik/traefik/v2Go

  fixed in 2.3.0-rc6

• github.com/containous/traefikGo

  From 1.5.0-rc5 · fixed in 1.7.26

• github.com/containous/traefik/v2Go

  fixed in 2.2.8

• github.com/traefik/traefik/v2Go

  From 2.3.0-rc1 · fixed in 2.3.0-rc6

• github.com/containous/traefik/v2Go

  From 2.3.0-rc1 · fixed in 2.3.0-rc3

• github.com/traefik/traefik/apiGo

  From 1.5.0-rc5 · fixed in 1.7.26

• github.com/traefik/traefik/v2/pkg/apiGo

  fixed in 2.3.0-rc6

• github.com/traefik/traefik/v2/pkg/apiGo

  From 2.3.0-rc1 · fixed in 2.3.0-rc6

• github.com/containous/traefik/apiGo

  From 1.5.0-rc5 · fixed in 1.7.26

• github.com/containous/traefik/v2/pkg/apiGo

  fixed in 2.2.8

• github.com/containous/traefik/v2/pkg/apiGo

  From 2.3.0-rc1 · fixed in 2.3.0-rc3

References 7