Multiple Vulnerabilities Discovered in Aiohttp: HTTP Response Splitting, Host Header Handling, and More

Aiohttp allowed multiple Host headers to be accepted, potentially bypassing security checks in reverse proxies. This could lead to requests being processed by privileged sub-applications when using `Application.add_domain()`.

An attacker could inject extra headers into HTTP responses by manipulating the `reason` parameter when creating a `Response` object. This could lead to unexpected behavior and potential exploits.

Aiohttp lacked sufficient restrictions on trailer header handling, potentially leading to uncapped memory usage when processing large requests or responses.

Aiohttp performed late size enforcement for non-file multipart form fields, potentially leading to a denial-of-service condition if an attacker sends a large, crafted multipart request.

Aiohttp leaked Cookie and Proxy-Authorization headers during cross-origin redirects, potentially exposing sensitive information to unintended parties.

An unbounded DNS cache in TCPConnector could lead to excessive memory usage and a denial-of-service if the application makes requests to a large number of hosts.

On Windows, the static resource handler may expose NTLMv2 remote path information, potentially leading to credential theft.

An attacker could inject CRLF sequences into the `content_type` parameter when constructing multipart requests, potentially leading to header injection exploits.