FlawAtlas
Search the atlas
CVE-2023-47106 Moderate

Traefik incorrectly processes fragment in the URL, leads to Authorization Bypass in github.com/traefik/traefik

Traefik incorrectly processes fragment in the URL, leads to Authorization Bypass in github.com/traefik/traefik

Exploit probability 0.6%
Published August 21, 2024
Required by Not available
Last source change August 7, 2026

02 / AFFECTED SOFTWARE

Affected packages

Go github.com/traefik/traefik/v2
Go github.com/traefik/traefik/v3
Go github.com/traefik/traefik
Go github.com/traefik/traefik/v2
Go github.com/traefik/traefik/v3
Unknown Unknown

222 explicit affected versions

03 / CONNECTIONS

Connected vulnerabilities

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2023-47106

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.

View original source
Open Source Vulnerabilities GHSA-fvhj-4qfh-q2hm

### Summary 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 the RFC 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. ### Details For example, we have this Nginx configuration: ``` location /admin { deny all; return 403; } ``` This can be bypassed when the attacker is requesting to /#/../admin This won’t be vulnerable if the backend server follows the RFC and ignores any characters after the fragment. However, if Nginx is chained with another reverse proxy which automatically URL encode the character # (Traefik) the URL will become /%23/../admin And allow the attacker to completely bypass the Access Restriction from the Nginx Front-End proxy. Here is a diagram to summarize the attack: ![image](https://user-images.githubusercontent.com/47447167/278849578-34ca0546-99b4-44c8-8fc8-8e799c1f5069.png) ### PoC ![image (1)](https://user-images.githubusercontent.com/47447167/278849597-280f2e80-f2d7-4dd9-9662-b8f488fd5ff2.png) This is the POC docker I've set up. It contains Nginx, Traefik proxies and a backend server running PHP. https://drive.google.com/file/d/1vLnA0g7N7ZKhLNmHmuJ4JJjV_J2akNMt/view?usp=sharing ### Impact This allows the attacker to completely bypass the Access Restriction from Front-End proxy.

View original source
Open Source Vulnerabilities GO-2023-2376

Traefik incorrectly processes fragment in the URL, leads to Authorization Bypass in github.com/traefik/traefik

View original source

05 / REFERENCES

Further evidence