CVE-2023-47641 Affecting python-aiohttp package, versions <3.8.1-1
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-DEBIAN13-PYTHONAIOHTTP-6057933
- published 15 Nov 2023
- disclosed 14 Nov 2023
Introduced: 14 Nov 2023
CVE-2023-47641 Open this link in a new tabHow to fix?
Upgrade Debian:13
python-aiohttp
to version 3.8.1-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python-aiohttp
package and not the python-aiohttp
package as distributed by Debian
.
See How to fix?
for Debian:13
relevant fixed versions and status.
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.