GHSA-cmxv-58fp-fm3g: Infoleak
Impact When redirect following is enabled (followRedirect(true)), AsyncHttpClient forwards Authorization and Proxy-Authorization headers along with Realm credentials to arbitrary redirect targets regardless of domain, scheme, or port changes. This leaks credentials on cross-domain redirects and HTTPS-to-HTTP downgrades.
Additionally, even when stripAuthorizationOnRedirect is set to true, the Realm object containing plaintext credentials is still propagated to the redirect request, causing credential re-generation for Basic and Digest authentication schemes via NettyRequestFactory.
An attacker who controls a redirect target (via open redirect, DNS rebinding, or MITM on HTTP) can capture Bearer tokens, Basic auth credentials, or any other Authorization header value.
Patches Fixed in version 3.0.9. Users should upgrade immediately.
The fix automatically strips Authorization and Proxy-Authorization headers and clears Realm credentials whenever a redirect crosses origin boundaries (different scheme, host, or port) or downgrades from HTTPS to HTTP.
Workarounds For users unable to upgrade, set (stripAuthorizationOnRedirect(true)) in the client config and avoid using Realm-based authentication with redirect following enabled. Note that (stripAuthorizationOnRedirect(true)) alone is insufficient on versions prior to 3.0.9 because the Realm bypass still re-generates credentials.
Alternatively, disable redirect following (followRedirect(false)) and handle redirects manually with origin validation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.asynchttpclient:async-http-clientto a version that resolves this vulnerability.Fixed in 3.0.9 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.0.9 - Configuration
Set stripAuthorizationOnRedirect(true) in the client configuration; on versions prior to 3.0.9, this setting is insufficient by itself, so do not use Realm-based authentication with redirect following enabled.
AsyncHttpClient stripAuthorizationOnRedirect = true - Configuration
Disable redirect following with followRedirect(false) and handle redirects manually with origin validation.
AsyncHttpClient followRedirect = false
Event History
Frequently Asked Questions
What is the severity of GHSA-cmxv-58fp-fm3g?
GHSA-cmxv-58fp-fm3g is classified as a high severity vulnerability due to the potential exposure of sensitive credentials.
How do I fix GHSA-cmxv-58fp-fm3g?
To fix GHSA-cmxv-58fp-fm3g, upgrade AsyncHttpClient to version 3.0.9 or later.
What are the implications of GHSA-cmxv-58fp-fm3g?
The implications of GHSA-cmxv-58fp-fm3g include unintentional credential leaks during cross-domain redirects.
Which versions of AsyncHttpClient are affected by GHSA-cmxv-58fp-fm3g?
All versions prior to 3.0.9 of AsyncHttpClient are affected by GHSA-cmxv-58fp-fm3g.
What should I do if I cannot update to version 3.0.9 for GHSA-cmxv-58fp-fm3g?
If you cannot update to version 3.0.9, disable redirect following or implement additional security measures to mitigate Credential exposure.