Medium, CVSS 5.8MavenPublished
StaticFile.fromUrl can leak presence of a directory
CVE-2021-32643 · GHSA-6h7w-fc84-x7p6
- Affected
- Maven org.http4s:http4s-core >= 0.21.7, < 0.21.24; >= 0.22.0-M1, <= 0.22.0-M8; >= 0.23.0-M1, <= 0.23.0-M1; >= 1.0.0-M1, <= 1.0.0-M22
- Fixed in
- 0.22.0-RC10.23.0-RC11.0.0-M230.21.24· Vendor fix available
- Issue
- 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…
Recommended action: Upgrade to 1.0.0-M23 (pre-release), 0.23.0-RC1 (pre-release), 0.22.0-RC1 (pre-release) or 0.21.24 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.