http4k: `DigestAuthProvider.verify` did not bind to request URI
http4k
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.http4k:http4k-security-digest Maven |
|
|
http4k
| Product | Affected | Fixed in |
|---|---|---|
| org.http4k:http4k-security-digest Maven |
|
|
http4k is a functional toolkit for Kotlin HTTP applications. Prior to 4.51.0.0, 5.42.0.0, and 6.50.0.0, DigestAuthProvider.verify in http4k-security-digest does not compare the uri parameter in an Authorization: Digest response with the actual request URL. An attacker who captures a valid Digest authentication response can replay it against another URL served by the same realm, bypassing the per-request-URI binding and potentially gaining unauthorized read or write access. This issue is fixed in versions 4.51.0.0, 5.42.0.0, and 6.50.0.0.
From the CVE record · GitHub_M
DigestAuthProvider.verify in http4k-security-digest does not check that the URI in a Digest authentication response matches the requested URL. An attacker with a captured valid response can replay it against another URL in the same realm, potentially gaining unauthorized read or write access without authenticating for that URL.
Teams using Maven org.http4k:http4k-security-digest versions 4.0.0.0 to before 4.51.0.0, 5.0.0.0 to before 5.42.0.0, or 6.0.0.0 to before 6.50.0.0 should check their deployments.