http4k before 6.48.0.0 Cookie Scoping Bypass via BasicCookieStorage
- 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 (Maven artifact org.http4k:http4k-core) before 6.48.0.0, 5.42.0.0, and 4.51.0.0 ships a BasicCookieStorage (client-side cookie store used by ClientFilters.Cookies) that does not enforce RFC 6265 scoping rules for the cookie domain, path, and Secure attributes. When a single BasicCookieStorage instance is used to talk to more than one origin or scheme, cookies stored for one origin can be sent to other origins, and cookies marked Secure can be sent over plain HTTP, potentially disclosing session cookies or other sensitive values to unauthorized hosts or network observers. Clients that use a storage instance for a single origin are not affected.
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-coreMaven
From 6.0.0.0 · fixed in 6.48.0.0
- org.http4k:http4k-coreMaven
From 5.0.0.0 · fixed in 5.42.0.0
- org.http4k:http4k-coreMaven
fixed in 4.51.0.0