Traefik has a possible vulnerability with the path matchers
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.11.24, 3.3.6, 3.4.0-rc2, 2.11.23
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- traefik traefik
fixed in 2.11.24; fixed in 3.3.6; From 3.4.0-rc1 · fixed in 3.4.0-rc2
- github.com/traefik/traefikGo
All versions
- github.com/traefik/traefik/v2Go
fixed in 2.11.23
- github.com/traefik/traefik/v3Go
fixed in 3.3.6; From 3.4.0-rc1 · fixed in 3.4.0-rc2
- github.com/traefik/traefikGo
through 1.7.34
- github.com/traefik/traefik/v3Go
fixed in 3.3.6
- github.com/traefik/traefik/v3Go
From 3.4.0-rc1 · fixed in 3.4.0-rc2