CVE-2023-47641 describes an HTTP protocol inconsistency vulnerability in aiohttp, an asynchronous HTTP client/server framework for Python. This flaw allows an attacker to bypass proxy rules and poison sockets by manipulating Content-Length and Transfer-Encoding headers, potentially leading to unauthorized access or redirection of users. With a CVSS score of 6.5 (Medium), the vulnerability has a network attack vector and low attack complexity, impacting confidentiality and integrity. There is currently no evidence of active exploitation, public exploit code (Metasploit, Nuclei, ExploitDB), or significant community discussion surrounding this CVE.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
< 3.8.0CPE matchmatch criteria | cpe:2.3:a:aiohttp:aiohttp:*:*:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.1 Bluesky, 0.0 Mastodon, and 0.4 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.0 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Aiohttp has inconsistent interpretation of `Content-Length` vs. `Transfer-Encoding` differing in C and Python fallbacks
Nov 14, 2023Inconsistent interpretation of `Content-Length` vs. `Transfer-Encoding` in aiohttp
Nov 14, 2023python-aiohttp: inconsistent interpretation of `Content-Length` vs. `Transfer-Encoding`
Nov 14, 2023