aio-libs aiohttp up to 3.7.x Header request smuggling

Summaryinfo

A vulnerability labeled as problematic has been found in aio-libs aiohttp up to 3.7.x. This vulnerability affects unknown code of the component Header Handler. Such manipulation leads to request smuggling. This vulnerability is uniquely identified as CVE-2023-47641. The attack can be launched remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in aio-libs aiohttp up to 3.7.x. It has been rated as problematic. Affected by this issue is an unknown part of the component Header Handler. The manipulation with an unknown input leads to a request smuggling vulnerability. Using CWE to declare the problem leads to CWE-444. The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. Impacted is integrity. CVE summarizes:

aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Affected versions of aiohttp have a security vulnerability regarding the inconsistent interpretation of the http protocol. HTTP/1.1 is a persistent protocol, if both Content-Length(CL) and Transfer-Encoding(TE) header values are present it can lead to incorrect interpretation of two entities that parse the HTTP and we can poison other sockets with this incorrect interpretation. A possible Proof-of-Concept (POC) would be a configuration with a reverse proxy(frontend) that accepts both CL and TE headers and aiohttp as backend. As aiohttp parses anything with chunked, we can pass a chunked123 as TE, the frontend entity will ignore this header and will parse Content-Length. The impact of this vulnerability is that it is possible to bypass any proxy rule, poisoning sockets to other users like passing Authentication Headers, also if it is present an Open Redirect an attacker could combine it to redirect random users to another website and log the request. This vulnerability has been addressed in release 3.8.0 of aiohttp. Users are advised to upgrade. There are no known workarounds for this vulnerability.

The weakness was disclosed 11/14/2023. The advisory is available at github.com. This vulnerability is handled as CVE-2023-47641 since 11/07/2023. The technical details are unknown and an exploit is not available.

The vulnerability scanner Nessus provides a plugin with the ID 214900 (Debian dla-4041 : python-aiohttp-doc - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 3.8.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (214900). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• aio-libs

Name

• aiohttp

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7

License

• open-source

Website

• Product: https://github.com/aio-libs/aiohttp/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion