Access-control bypass via hop-by-hop header stripping
Published Sep 19, 2024 · Updated Sep 20, 2024
Header trust bypass in Traefik Proxy before 2.11.9 and 3.0.0 through 3.1.2 allows remote attackers to alter forwarded identity data. Traefik's HTTP/1.1 path honors names in the Connection header as hop-by-hop fields after adding trusted X-Forwarded headers, deleting those fields before the backend receives them. Exploitation requires a backend that trusts an affected header; an attacker can substitute an underscore-form alias to bypass its access controls.
Summary
What happened
Header trust bypass in Traefik Proxy before 2.11.9 and 3.0.0 through 3.1.2 allows remote attackers to alter forwarded identity data. Traefik's HTTP/1.1 path honors names in the Connection header as hop-by-hop fields after adding trusted X-Forwarded headers, deleting those fields before the backend receives them. Exploitation requires a backend that trusts an affected header; an attacker can substitute an underscore-form alias to bypass its access controls.
The record
- CVE
- CVE-2024-45410
- Published
- Sep 19, 2024
- Updated
- Sep 20, 2024
- Vendor
- Traefik Labs
- Product
- Traefik Proxy
- Classifications
- CWE-348, CWE-345, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2024CVE publishedPublication date reported by the CVE source.
- Sep 20, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.11.9
- Affected versionversion=< 2.11.9
- Affected versionversion=>= 3.0.0, < 3.1.3
- Affected versionversion=3.0.0 <3.1.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor Connection-header proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo