http4k before 6.49.0.0 Host Header Routing Bypass via reverseProxy
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 4.51.0.0, 5.42.0.0 and 6.49.0.0.
http4k (Maven package org.http4k:http4k-core) before 6.49.0.0, 5.42.0.0 and 4.51.0.0 uses substring (Contains) matching on the Host header by default in reverseProxy() and reverseProxyRouting() when dispatching to configured virtual hosts. If these functions are deployed as a public-facing inbound HTTP handler with two or more configured virtual hosts, a remote attacker can supply a Host header that merely contains a configured vhost name (for example Host: admin.evil.com for a vhost configured as "admin") and be routed to that vhost, bypassing routing-based authorization. The intended outbound-dispatch and test-time uses, where the Host value is set by the calling application, are not affected.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| http4k | <4.51.0.0, >=5.0.0.0 <5.42.0.0, >=6.0.0.0 <6.49.0.0 | 4.51.0.0, 5.42.0.0, 6.49.0.0 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket