Memory exhaustion in http4s-async-http-client with large or malicious compressed responses
ImpactA 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](https://app.snyk.io/vuln/SNYK-JAVA-IONETTY-564897).PatchesUpgrade to http4s-async-http-client >= 0.21.8.  All 1.0 milestones are also safe.WorkaroundsAdd an explicit runtime dependency on async-http-client's netty dependencies that evicts them to an unaffected version:Referenceshttps://app.snyk.io/vuln/SNYK-JAVA-IONETTY-564897https://github.com/http4s/http4s/issues/3681For more informationIf you have any questions or comments about this advisory:Open an issue in [http4s](https://github.com/http4s/http4s/issues/new)Contact a maintainer privately per [http4s' security policy](https://github.com/http4s/http4s/blob/master/SECURITY.md#reporting-a-vulnerability)