http4k before 6.48.0.0 Digest Authentication Replay Protection Bypass
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.48.0.0, 5.42.0.0, 4.51.0.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
http4k's Digest authentication module (org.http4k:http4k-security-digest) before versions 6.48.0.0, 5.42.0.0 and 4.51.0.0 defaults the nonceVerifier parameter of ServerFilters.DigestAuth and DigestAuthProvider to { true }, so every nonce is accepted regardless of its value, age, or prior use. Applications relying on this default have no replay protection on Digest authentication: an attacker who can capture a valid 'Authorization: Digest' response (for example by observing network traffic or reading logs) can replay it indefinitely against the same protected resource.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- http4k http4k
From 6.0.0.0 · fixed in 6.48.0.0
- http4k http4k
From 5.0.0.0 · fixed in 5.42.0.0
- http4k http4k
fixed in 4.51.0.0
- org.http4k:http4k-security-digestMaven
From 6.0.0.0 · fixed in 6.48.0.0
- org.http4k:http4k-security-digestMaven
From 5.0.0.0 · fixed in 5.42.0.0
- org.http4k:http4k-security-digestMaven
fixed in 4.51.0.0