CVE-2024-45410
published 2024-09-19CVE-2024-45410: 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…
PriorityP345high7.5CVSS 3.1
AVNACLPRNUINSUCNIHAN
EPSS
1.51%
71.3th percentile
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.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | fabiolb_fabio | >= 0 < 1.6.6 | 1.6.6 |
| github.com | traefik_traefik | >= 0 < 2.11.9 | 2.11.9 |
| github.com | traefik_traefik_v2 | >= 0 < 2.11.9 | 2.11.9 |
| github.com | traefik_traefik_v2 | >= 2.11.9 < 2.11.38 | 2.11.38 |
| github.com | traefik_traefik_v3 | >= 3.0.0-beta3 < 3.1.3 | 3.1.3 |
| github.com | traefik_traefik_v3 | >= 3.1.3 < 3.6.9 | 3.6.9 |
| traefik | traefik | < 2.11.9 | 2.11.9 |
| traefik | traefik | — | — |
| traefik | traefik | >= 3.0.0 < 3.1.3 | 3.1.3 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
ghsa9.8CRITICAL
osv9.8CRITICAL
vendor_redhat9.8CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`) in github.com/traefik/traefik
osv·2026-03-10·CVSS 7.5
CVE-2026-29054 [HIGH] traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`) in github.com/traefik/traefik
traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`) in github.com/traefik/traefik
traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`) in github.com/traefik/traefik
GHSA
traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`)
ghsa·2026-03-04·CVSS 7.5
CVE-2026-29054 [HIGH] CWE-178 traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`)
traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`)
## Impact
There is a potential vulnerability in Traefik managing the `Connection` header with `X-Forwarded` headers.
When Traefik processes HTTP/1.1 requests, the protection put in place to prevent the removal of Traefik-managed `X-Forwarded` headers (such as `X-Real-Ip`, `X-Forwarded-Host`, `X-Forwarded-Port`, etc.) via the `Connection` header does not handle case sensitivity correctly. The `Connection` tokens are compared case-sensitively against the protected header names, but the actual header deletion operates case-insensitively. As a result, a remote unauthenticated client can use lowercase `Connection` tokens (e.g. `Connection: x-real-i
OSV
traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`)
osv·2026-03-04·CVSS 7.5
CVE-2026-29054 [HIGH] traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`)
traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`)
## Impact
There is a potential vulnerability in Traefik managing the `Connection` header with `X-Forwarded` headers.
When Traefik processes HTTP/1.1 requests, the protection put in place to prevent the removal of Traefik-managed `X-Forwarded` headers (such as `X-Real-Ip`, `X-Forwarded-Host`, `X-Forwarded-Port`, etc.) via the `Connection` header does not handle case sensitivity correctly. The `Connection` tokens are compared case-sensitively against the protected header names, but the actual header deletion operates case-insensitively. As a result, a remote unauthenticated client can use lowercase `Connection` tokens (e.g. `Connection: x-real-i
GHSA
Fabio allows HTTP clients to manipulate custom headers it adds
ghsa·2025-05-29·CVSS 9.8
CVE-2025-48865 [CRITICAL] CWE-345 Fabio allows HTTP clients to manipulate custom headers it adds
Fabio allows HTTP clients to manipulate custom headers it adds
### Summary
Fabio allows clients to remove X-Forwarded headers (except X-Forwarded-For) due to a vulnerability in how it processes hop-by-hop headers.
Fabio adds HTTP headers like X-Forwarded-Host and X-Forwarded-Port when routing requests to backend applications. Since the receiving application should trust these headers, allowing HTTP clients to remove or modify them creates potential security vulnerabilities.
However, it was found that some of these custom headers can indeed be removed and, in certain cases, manipulated. The attack relies on the behavior that headers can be defined as hop-by-hop via the HTTP Connection header. By setting the following connection header, the X-Forwarded-Host header can, for example, be rem
OSV
Fabio allows HTTP clients to manipulate custom headers it adds
osv·2025-05-29·CVSS 9.8
CVE-2025-48865 [CRITICAL] Fabio allows HTTP clients to manipulate custom headers it adds
Fabio allows HTTP clients to manipulate custom headers it adds
### Summary
Fabio allows clients to remove X-Forwarded headers (except X-Forwarded-For) due to a vulnerability in how it processes hop-by-hop headers.
Fabio adds HTTP headers like X-Forwarded-Host and X-Forwarded-Port when routing requests to backend applications. Since the receiving application should trust these headers, allowing HTTP clients to remove or modify them creates potential security vulnerabilities.
However, it was found that some of these custom headers can indeed be removed and, in certain cases, manipulated. The attack relies on the behavior that headers can be defined as hop-by-hop via the HTTP Connection header. By setting the following connection header, the X-Forwarded-Host header can, for example, be rem
OSV
HTTP client can manipulate custom HTTP headers that are added by Traefik in github.com/traefik/traefik
osv·2024-09-26
CVE-2024-45410 HTTP client can manipulate custom HTTP headers that are added by Traefik in github.com/traefik/traefik
HTTP client can manipulate custom HTTP headers that are added by Traefik in github.com/traefik/traefik
HTTP client can manipulate custom HTTP headers that are added by Traefik in github.com/traefik/traefik
GHSA
HTTP client can manipulate custom HTTP headers that are added by Traefik
ghsa·2024-09-19·CVSS 9.8
CVE-2024-45410 [CRITICAL] CWE-345 HTTP client can manipulate custom HTTP headers that are added by Traefik
HTTP client can manipulate custom HTTP headers that are added by Traefik
### Impact
There is a vulnerability in Traefik that allows the client to remove the X-Forwarded headers (except the header X-Forwarded-For).
### Patches
- https://github.com/traefik/traefik/releases/tag/v2.11.9
- https://github.com/traefik/traefik/releases/tag/v3.1.3
### Workarounds
No workaround.
### For more information
If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).
Original Description
### Summary
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 remo
OSV
HTTP client can manipulate custom HTTP headers that are added by Traefik
osv·2024-09-19·CVSS 9.8
CVE-2024-45410 [CRITICAL] HTTP client can manipulate custom HTTP headers that are added by Traefik
HTTP client can manipulate custom HTTP headers that are added by Traefik
### Impact
There is a vulnerability in Traefik that allows the client to remove the X-Forwarded headers (except the header X-Forwarded-For).
### Patches
- https://github.com/traefik/traefik/releases/tag/v2.11.9
- https://github.com/traefik/traefik/releases/tag/v3.1.3
### Workarounds
No workaround.
### For more information
If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).
Original Description
### Summary
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 remo
Red Hat
traefik: HTTP client can manipulate custom HTTP headers that are added by Traefik
vendor_redhat·2024-09-19·CVSS 9.8
CVE-2024-45410 [CRITICAL] CWE-345 traefik: HTTP client can manipulate custom HTTP headers that are added by Traefik
traefik: HTTP client can manipulate custom HTTP headers that are added by Traefik
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
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-09-19
Published