StaticFile.fromUrl can leak presence of a directory
http4s
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-core Maven |
|
|
http4s
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-core Maven |
|
|
Http4s is a Scala interface for HTTP services. `StaticFile.fromUrl` can leak the presence of a directory on a server when the `URL` scheme is not `file://`, and the URL points to a fetchable resource under its scheme and authority. The function returns `F[None]`, indicating no resource, if `url.getFile` is a directory, without first checking the scheme or authority of the URL. If a URL connection to the scheme and URL would return a stream, and the path in the URL exists as a directory on the server, the presence of the directory on the server could be inferred from the 404 response. The contents and other metadata about the directory are not exposed. This affects http4s versions: 0.21.7 through 0.21.23, 0.22.0-M1 through 0.22.0-M8, 0.23.0-M1, and 1.0.0-M1 through 1.0.0-M22. The [patch](https://github.com/http4s/http4s/commit/52e1890665410b4385e37b96bc49c5e3c708e4e9) is available in the following versions: v0.21.24, v0.22.0-M9, v0.23.0-M2, v1.0.0-M23. As a workaround users can avoid calling `StaticFile.fromUrl` with non-file URLs.
From the CVE record · GitHub_M
In affected http4s versions, `StaticFile.fromUrl` can reveal whether a directory exists on the server. An attacker can infer its presence from a 404 response when the application calls the function with a non-file URL pointing to a fetchable resource. Directory contents and other metadata are not exposed.
Check applications using Maven `org.http4s:http4s-core` versions >=0.21.7 <0.21.24, >=0.22.0-M1 <0.22.0-RC1, >=0.23.0-M1 <0.23.0-RC1, or >=1.0.0-M1 <1.0.0-M23.