github.com/traefik/traefik/v3 is vulnerable to Exposure of Data Element to Wrong Session
70
CVE Score
High
Exposure of Data Element to Wrong Session
Before the fix, Traefik's ForwardAuth middleware sent each client's authentication subrequest to the configured auth server over a connection pool shared by all clients of the middleware. When that auth server used connection-bound NTLM or Negotiate authentication (as IIS Windows Authentication does), an unauthenticated client on a separate frontend connection could reuse a connection already authenticated for a victim and receive the victim's identity through authResponseHeaders, reaching backends as that user. On 3.7 releases that include the Ingress NGINX provider, its auth-url external requests were exposed the same way. The fix dedicates an auth-server transport to each frontend connection through kerberos.NewRoundTripper.
Upgrade the github.com/traefik/traefik/v3 package to 3.7.16 or later.
You are affected if you are using a version that falls within the vulnerable range and configure the ForwardAuth middleware against an authentication server using connection-bound NTLM or Negotiate authentication, with the endpoint reachable to unauthenticated clients.
3.0.0 - 3.7.15
Fixed in 3.7.16github.com/traefik/traefik/v3 is vulnerable to Exposure of Data Element to Wrong Session in versions 3.0.0 - 3.7.15.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.