CyberRota Analysis
AI-GeneratedTraefik versions prior to 2.11.53, 3.6.24, and 3.7.9 are vulnerable to an issue where an unauthenticated attacker can exploit the HTTP/2 or HTTP/3 CONNECT request handling, allowing them to smuggle responses that may contain sensitive information from other clients. This desynchronization can lead to unauthorized access to authenticated or private content, particularly affecting users utilizing the ForwardAuth middleware. Organizations using affected versions of Traefik should prioritize upgrading to the patched versions to mitigate this high-severity vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.53, 3.6.24, and 3.7.9, Traefik's default HTTP reverse proxy forwards a plain HTTP/2 or HTTP/3 CONNECT request and its body to an HTTP/1.1 upstream through a shared net/http.Transport. When the upstream answers the CONNECT with a keep-alive non-2xx response and does not drain the body, Traefik returns the desynchronized backend socket to its shared pool and reuses it for other clients. An unauthenticated attacker can use this behavior to make a different client read the attacker's smuggled response, which can include authenticated or private content from another request. The ForwardAuth middleware with forwardBody true and preserveRequestMethod true can re-issue a CONNECT with the buffered body attached, exposing the auth-client pool to the same desynchronization. This issue is fixed in 2.11.53, 3.6.24, and 3.7.9.