HTTP Request Smuggling Affecting aiohttp package, versions [,3.8.6)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 IDSNYK-PYTHON-AIOHTTP-6057353
- published15 Nov 2023
- disclosed14 Nov 2023
- creditBen Kallus
Introduced: 14 Nov 2023
CVE-2023-47627 (opens in a new tab)How to fix?
Upgrade aiohttp to version 3.8.6 or higher.
Overview
Affected versions of this package are vulnerable to HTTP Request Smuggling via the HTTP parser. An attacker can manipulate the header parsing, leading to potential request smuggling by exploiting the incorrect usage of the int constructor for Content-Length values, improper handling of NUL, CR, and LF in header values, and improper stripping of whitespace before colon in HTTP headers.
Note:
This is only exploitable if AIOHTTP_NO_EXTENSIONS is enabled or not using a prebuilt wheel.
Workaround
This vulnerability can be mitigated by verifying that a Content-Length value consists only of ASCII digits before parsing, rejecting all messages with NUL, CR, or LF in a header value, and rejecting all messages with whitespace before a colon in a header field.