UnratedMavenPublished
Memory exhaustion in http4s-async-http-client with large or malicious compressed responses
GHSA-8hxh-r6f7-jf45
- Affected
- Maven org.http4s:http4s-async-http-client_2.12 <= 0.21.7
- Fixed in
- 0.21.8· Vendor fix available
- Issue
- Impact A server we connect to with http4s-async-http-client could theoretically respond with a large or malicious compressed stream and exhaust memory in the client JVM. It does not affect http4s servers, other client backends, or clients that speak only to trusted servers. This is related to a transitive dependency on netty-codec-4.1.45.Final, which is affected by CVE-2020-11612. Patches Upgrade to http4s-async-http-client = 0.21.8. All 1.0 milestones are also safe. Workarounds Add an explicit runtime dependency on async-http-client's netty dependencies that evicts them to an unaffected version: References https://app.snyk.io/vuln/SNYK-JAVA-IONETTY-564897 https://github.com/http4s/http4s/issues/3681 For more information If you have any questions or comments about this advisory: Open an issue in http4s Contact a maintainer privately per http4s' security policy
Recommended action: Upgrade to 0.21.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.