async-http-client: AsyncHttpClient: Incomplete origin checks in the default cookie store allow cookie tossing onto public-suffix and IP-address hosts
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.16.0 until 3.0.14, ThreadSafeCookieStore incompletely validates cookie Domain attributes. Missing private-section and default public-suffix rules, absent A-label normalization, locale-sensitive lowercasing, public-suffix host-only handling, and numeric or IP host checks allow one origin to store a cookie later sent to another origin. Applications sharing one client across trust domains can therefore receive attacker-injected cookies and may be exposed to session fixation. This issue is fixed in version 3.0.14.
Text from CVE List
Affected versions 2
- async-http-clientaffected: >= 3.0.11, < 3.0.14CVE List
- async-http-clientaffected: >= 2.16.0, <= 2.16.1CVE List
References 3
- github.com/AsyncHttpClient/async-http-client/commit/7dc5bbc2d0a48aa2a9caf089a626dcfd333168e9Fixvia CVE List
- github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.14Fixvia CVE List
- github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-qjr7-w8pj-pmv9Advisoryvia CVE List