Advisory

GHSA-8qpw-xqxj-h4r2

Also known as: CVE-2024-23829, PYSEC-2024-26

Summary

aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-01-29 22:30 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

aiohttp

PyPI · All systems

Affected

  • introduced 0, fixed 3.9.2 (ecosystem)

Fixed versions

3.9.2

Fix

  • Fixed version 3.9.2
    pip install --upgrade aiohttp==3.9.2

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences