StaticFile.fromUrl can leak presence of a directory
Package
Affected versions
>= 0.21.7, < 0.21.24
>= 0.22.0-M1, <= 0.22.0-M8
= 0.23.0-M1
>= 1.0.0-M1, <= 1.0.0-M22
Patched versions
0.21.24
0.22.0-RC1
0.23.0-RC1
1.0.0-M23
Description
Published by the National Vulnerability Database
May 27, 2021
Reviewed
May 27, 2021
Published to the GitHub Advisory Database
May 28, 2021
Last updated
Feb 1, 2023
Impact
StaticFile.fromUrl
can leak the presence of a directory on a server when theURL
scheme is notfile://
, and the URL points to a fetchable resource under its scheme and authority. The function returnsF[None]
, indicating no resource, ifurl.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:
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.fromUrl
with non-file URLs.For more information
If you have any questions or comments about this advisory:
References