Impact
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
- 1.0.0-M1 through 1.0.0-M22
Patches
The patch is available in the following versions:
- v0.21.24
- v0.22.0-RC1
- v0.23.0-RC1
- v1.0.0-M23
Note: a previous version of this advisory incorrectly referred to 0.22.0-M9 and 0.23.0-M2.
Workarounds
Don't call StaticFile.fromUrl with non-file URLs.
For more information
If you have any questions or comments about this advisory:
Impact
StaticFile.fromUrlcan leak the presence of a directory on a server when theURLscheme is notfile://, and the URL points to a fetchable resource under its scheme and authority. The function returnsF[None], indicating no resource, ifurl.getFileis 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:
Patches
The patch is available in the following versions:
Note: a previous version of this advisory incorrectly referred to 0.22.0-M9 and 0.23.0-M2.
Workarounds
Don't call
StaticFile.fromUrlwith non-file URLs.For more information
If you have any questions or comments about this advisory: