Default CORS config allows any origin with credentials
http4s
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-server_2.13.0-M5 Maven |
| No fix yet |
| org.http4s:http4s-server_3 Maven |
|
|
http4s
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-server_2.13.0-M5 Maven |
| No fix yet |
| org.http4s:http4s-server_3 Maven |
|
|
| org.http4s:http4s-server_2.10 Maven |
|
| No fix yet |
| org.http4s:http4s-server_2.11 Maven |
| No fix yet |
| org.http4s:http4s-server_2.12 Maven |
|
|
| org.http4s:http4s-server_2.13 Maven |
|
|
Http4s is a minimal, idiomatic Scala interface for HTTP services. In http4s versions 0.21.26 and prior, 0.22.0 through 0.22.2, 0.23.0, 0.23.1, and 1.0.0-M1 through 1.0.0-M24, the default CORS configuration is vulnerable to an origin reflection attack. The middleware is also susceptible to a Null Origin Attack. The problem is fixed in 0.21.27, 0.22.3, 0.23.2, and 1.0.0-M25. The original `CORS` implementation and `CORSConfig` are deprecated. See the GitHub GHSA for more information, including code examples and workarounds.
From the CVE record · GitHub_M
The default CORS configuration in affected http4s versions reflects origins, and the middleware is also susceptible to a null-origin attack. A remote attacker can exploit these CORS weaknesses when an affected configuration is in use; the input does not specify authentication or user-interaction requirements.
Engineers running the listed Maven http4s-server packages should check the affected version ranges, including the listed packages for which no fix is available.