aiohttp
Affected
- introduced
0, fixed3.9.2(ecosystem)
Fixed versions
3.9.2
Fix
- Fixed version
3.9.2pip install --upgrade aiohttp==3.9.2
Advisory
Also known as: CVE-2024-23829, PYSEC-2024-26
aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators
Summary
Security-sensitive parts of the *Python HTTP parser* retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input.
Details
These problems are rooted in pattern matching protocol elements, previously improved by PR #3235 and GHSA-gfw2-4jvh-wgfg:
HTTP/(\d).(\d) lacked another backslash to clarify that the separator should be a literal dot, not just *any* Unicode code point (result: HTTP/(\d)\.(\d)).token.PoCGET / HTTP/1ö1GET / HTTP/1.𝟙GET/: HTTP/1.1Content-Encoding?: chunked
Impact
Primarily concerns running an aiohttp server without llhttp:
-----
Patch: https://github.com/aio-libs/aiohttp/pull/8074/files
Medium Basis: The source's own band: MODERATE
0, fixed 3.9.2 (ecosystem)3.9.2
3.9.2pip install --upgrade aiohttp==3.9.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0