نسخههای متأثر
- نسخههای متأثر
- <= 0.23.34
- نسخهٔ اصلاحشده
- 0.23.35
- نسخههای متأثر
- >= 1.0.0-M1, <= 1.0.0-M46
- نسخهٔ اصلاحشده
- 1.0.0-M47
- نسخههای متأثر
- <= 0.23.34
- نسخهٔ اصلاحشده
- 0.23.35
- نسخههای متأثر
- >= 1.0.0-M1, <= 1.0.0-M46
- نسخهٔ اصلاحشده
- 1.0.0-M47
- نسخههای متأثر
- <= 0.23.34
- نسخهٔ اصلاحشده
- 0.23.35
بهرهبرداری
شرح آسیبپذیری
The static content handlers ResourceService and WebjarService URL decode each path segment and then reject only segments that are exactly "", ".", or "..". A percent-encoded separator (%2F) lets an attacker smuggle a ../ segment past that filter and escape the configured base, reading resources that should not be public.
On Windows, a similar attack exists with (%5C).
Impact
Disclosure of classpath or webjar resources outside the configured base.
Preconditions
Application uses
ResourceService(with a non-root base path) orWebjarServiceAt least one classpath entry is served from a directory (e.g.
sbt run, exploded .war)Backend forwards
%2F/%5Cwithout normalizing (e.g., Ember, Blaze)
Fixes
The patch rejects any decoded path segment containing / (%2F) or \ (%5C) with a 400 Bad Request in ResourceService and WebjarService.
FileService was not exploitable, but the same guards are applied for consistency and to remove its reliance on path normalization.
Workarounds
Deploy as a fat jar, with no filesystem directories on the classpath.
Front the service with a proxy that rejects/normalizes
%2Fand%5Cin the request path.
پیوندها
- https://github.com/advisories/GHSA-crq5-92j2-j7wv
- https://github.com/http4s/http4s
- https://github.com/http4s/http4s/commit/bcd99cdc1342ef58a0f132acb814af06a668a8d3
- https://github.com/http4s/http4s/releases/tag/v0.23.35
- https://github.com/http4s/http4s/releases/tag/v1.0.0-M47
- https://github.com/http4s/http4s/security/advisories/GHSA-crq5-92j2-j7wv
گزارشدهندگان
- Lasering
- rossabaker
- samspills

