Host routing bypass via authority mismatch
Published Aug 17, 2021 · Updated Aug 4, 2024
Host header validation bypass in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3 allows remote attackers to evade routing rules. HAProxy evaluates switching rules against the HTTP Host header, then drops that header when forwarding to an HTTP/2 backend and reconstructs it from a conflicting :authority value. Exploitation requires HTTP/2 on both sides and can route a request under a different host identity than the proxy validated.
Summary
What happened
Host header validation bypass in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3 allows remote attackers to evade routing rules. HAProxy evaluates switching rules against the HTTP Host header, then drops that header when forwarding to an HTTP/2 backend and reconstructs it from a conflicting :authority value. Exploitation requires HTTP/2 on both sides and can route a request under a different host identity than the proxy validated.
The record
- CVE
- CVE-2021-39242
- Published
- Aug 17, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- HTTP/2 Host and authority mismatch request exampleproof 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