http4k: `DigestAuthProvider.verify` ignored configured algorithm and did not bind to request URI
- 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 4.51.0.0, 5.42.0.0, 6.50.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 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 ignores its configured algorithm parameter and verifies every Digest response with hardcoded MD5. Deployments configured for SHA-256 therefore receive weaker MD5-based verification, exposing Digest authentication to collision-related attack paths that depend on the hash function's collision resistance. This issue is fixed in versions 4.51.0.0, 5.42.0.0, and 6.50.0.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- http4k http4k
fixed in 4.51.0.0; From 5.0.0.0 · fixed in 5.42.0.0; From 6.0.0.0 · fixed in 6.50.0.0
- org.http4k:http4k-security-digestMaven
From 6.0.0.0 · fixed in 6.50.0.0
- org.http4k:http4k-security-digestMaven
From 5.0.0.0 · fixed in 5.42.0.0
- org.http4k:http4k-security-digestMaven
through 4.48.2.0