Http4s: DigestAuth allows replay of captured requests
http4s
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-ember-core_2.12 Maven |
|
|
| org.http4s:http4s-ember-core_2.13 Maven |
|
|
http4s
| Product | Affected | Fixed in |
|---|---|---|
| org.http4s:http4s-ember-core_2.12 Maven |
|
|
| org.http4s:http4s-ember-core_2.13 Maven |
|
|
1.0.0-M47| org.http4s:http4s-ember-core_3 Maven |
|
|
Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, DigestAuth replay protection records lastNc plus one instead of the highest nonce-count value it has accepted. When a legitimate client sends noncontiguous nc values because of parallel or retried requests, the stored counter remains below the accepted maximum, allowing a passive observer to replay a captured Authorization header multiple times. Successful replays execute authenticated requests, including state-changing operations, as the captured user. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
From the CVE record · GitHub_M
DigestAuth records an incorrect nonce-count value when a legitimate client sends noncontiguous values during parallel or retried requests. A passive observer who captures an Authorization header can then replay it multiple times, executing authenticated requests, including state-changing operations, as that user.
Check applications using Maven org.http4s:http4s-ember-core_2.12 below 0.23.35, or http4s-ember-core_2.13 or http4s-ember-core_3 below 0.23.35 or from 1.0.0-M1 through versions before 1.0.0-M47.