NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2024-23829: aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators

mediumCVSS 4.0 6.9 · 3.1 6.5GHSA-8qpw-xqxj-h4r2

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.

Published Jan 29, 2024 · Updated Nov 3, 2025

Affected packages

aiohttp

Ecosystem
PyPI
Affected
< 3.9.2
Fixed in
3.9.2
Check
pip show aiohttp

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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:

  1. The expression 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)).
  1. The HTTP version was permitting Unicode digits, where only ASCII digits are standards-compliant.
  1. Distinct regular expressions for validating HTTP Method and Header field names were used - though both should (at least) apply the common restrictions of rfc9110 token.

PoC

GET / HTTP/1ö1 GET / HTTP/1.𝟙 GET/: HTTP/1.1 Content-Encoding?: chunked

Impact

Primarily concerns running an aiohttp server without llhttp:

  1. behind a proxy: Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling.
  2. directly accessible or exposed behind proxies relaying malformed input: the unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities.

-----

Patch: https://github.com/aio-libs/aiohttp/pull/8074/files

Credited to pajod.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries