Backend routing bypass via conflicting Host authority
Published Apr 11, 2022 · Updated Aug 3, 2024
Improper HTTP/2 request handling in Red Hat OpenShift Container Platform 4.9 allows remote attackers to alter backend Host routing. HAProxy preserves a conflicting Host header instead of giving the HTTP/2 :authority pseudo-header precedence, so successive HTTP/2 hops can derive different backend host values. Exploitation requires an HTTP/2-to-HTTP/2 proxy chain and a crafted unauthenticated request; the mismatch can bypass proxy-layer hostname filtering and route traffic to an unintended backend.
Summary
What happened
Improper HTTP/2 request handling in Red Hat OpenShift Container Platform 4.9 allows remote attackers to alter backend Host routing. HAProxy preserves a conflicting Host header instead of giving the HTTP/2 :authority pseudo-header precedence, so successive HTTP/2 hops can derive different backend host values. Exploitation requires an HTTP/2-to-HTTP/2 proxy chain and a crafted unauthenticated request; the mismatch can bypass proxy-layer hostname filtering and route traffic to an unintended backend.
The record
- CVE
- CVE-2021-4047
- Published
- Apr 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform
- Classifications
- CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=OpenShift 4.9
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.
Public exploit references
No public exploit references are available in this record.
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