نسخههای متأثر
- نسخههای متأثر
- <= 0.23.34
- نسخهٔ اصلاحشده
- 0.23.35
- نسخههای متأثر
- <= 0.23.34
- نسخهٔ اصلاحشده
- 0.23.35
- نسخههای متأثر
- >= 1.0.0-M1, <= 1.0.0-M46
- نسخهٔ اصلاحشده
- 1.0.0-M47
- نسخههای متأثر
- >= 1.0.0-M1, <= 1.0.0-M46
- نسخهٔ اصلاحشده
- 1.0.0-M47
- نسخههای متأثر
- <= 0.23.34
- نسخهٔ اصلاحشده
- 0.23.35
بهرهبرداری
شرح آسیبپذیری
The DigestAuth replay defence stores lastNc + 1 rather than the nonce-count (nc) value it just accepted. When a legitimate client sends non-contiguous nc values (parallel or retried requests, as browsers do), the server's counter lags behind the highest nc seen, and a captured Authorization header can be replayed multiple times.
Impact
A passive observer can turn one captured Digest-authenticated request into several replayed authenticated (state-changing) requests, defeating the core replay protection Digest provides over Basic.
Preconditions
Application uses
DigestAuth.Attacker can passively observe at least one legitimate digest request.
Legitimate client emits an
ncmore than one greater than the last, for instance from a parallel or retried request.
Workarounds
Deploy over TLS so requests cannot be captured.
پیوندها
- https://github.com/advisories/GHSA-9xww-74xv-gjfp
- https://github.com/http4s/http4s
- https://github.com/http4s/http4s/commit/7f065101c45f3d86bc105e8fc6323c2c4a11471f
- 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-9xww-74xv-gjfp
گزارشدهندگان
- rossabaker
- morgen-peschke

