Update dependency org.asynchttpclient:async-http-client to v2.12.4 [SECURITY] #239
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.12.3
->2.12.4
GitHub Vulnerability Alerts
CVE-2024-53990
Summary
When making any HTTP request, the automatically enabled and self-managed
CookieStore
(aka cookie jar) will silently replace explicitly definedCookie
s with any that have the same name from the cookie jar. For services that operate with multiple users, this can result in one user'sCookie
being used for another user's requests.Details
This issue is described without security warnings here:
https://github.com/AsyncHttpClient/async-http-client/issues/1964
A PR to fix this issue has been made:
https://github.com/AsyncHttpClient/async-http-client/pull/2033
PoC
Cookie
to theCookieStore
Set-Cookie
, as shown in issue #1964 above.Cookie
is provided as a passthrough, like a JWT, and attempt to use it by explicitly providing it.Impact
This is generally going to be a problem for developers of backend services that implement third party auth features and use other features like token refresh. The moment a third party service responds by setting a cookie in the response, the
CookieStore
will effectively break almost every follow-up request (hopefully by being rejected, but possibly by revealing a different user's information).If your service sets cookies based on the response that happens here, it's possible to lead to even greater levels of exposure.
Workaroud
You can avoid this issue by disabling the
CookieStore
during client creation:Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.