Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2024-52304

aiohttp: aiohttp vulnerable to request smuggling due to incorrect parsing of chunk extensions

Overview

Published
18 Nov 2024
Modified
17 Jun 2026
Medium CVE
3 Registry packages
12 OS packages
7 Linux distributions
Yes Fix available

Description

aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.10.11, the Python parser parses newlines in chunk extensions incorrectly which can lead to request smuggling vulnerabilities under certain conditions. If a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or AIOHTTP_NO_EXTENSIONS is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections. Version 3.10.11 fixes the issue.

Source: OX vulnerability database

Severity

7.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Weakness: CWE-444

Affected packages · 3

Packages affected by CVE-2024-52304
EcosystemPackageVulnerableFixed in
PyPI aiohttp <3.10.11 3.10.11
Seal PyPI aiohttp >=2.3.9+sp0, <2.3.9+sp999>=3.0.8+sp0, <3.0.8+sp999>=3.6.2+sp0, <3.6.2+sp999>=3.8.5+sp0, <3.8.5+sp999>=3.8.6+sp0, <3.8.6+sp3+1 more 2.3.9+sp9993.0.8+sp9993.6.2+sp9993.8.5+sp9993.8.6+sp3
Seal PyPI seal-aiohttp >=2.3.9+sp1, <2.3.9+sp999>=3.0.8+sp1, <3.0.8+sp999>=3.6.2+sp1, <3.6.2+sp999>=3.8.5+sp1, <3.8.5+sp999>=3.8.6+sp1, <3.8.6+sp3+1 more 2.3.9+sp9993.0.8+sp9993.6.2+sp9993.8.5+sp9993.8.6+sp3

Open a package to see all its vulnerabilities.

Operating systems · 30 fixes

Red Hat 1 release · 1 package

affected 1
python-aiohttp
Red Hat fixes for CVE-2024-52304
ReleasePackageFixed in
7 python-aiohttp +1 affected

SUSE Linux Enterprise 3 releases · 2 packages

fixed 6
python3-aiohttp python311-aiohttp
SUSE Linux Enterprise fixes for CVE-2024-52304
ReleasePackageFixed inAdvisory
15.4 python3-aiohttp 3.6.0-150100.3.18.1 SUSE-SU-2024:4110-1
15.4 python311-aiohttp 3.9.3-150400.10.27.1 SUSE-SU-2024:4077-1
15.5 python3-aiohttp 3.6.0-150100.3.18.1 SUSE-SU-2024:4110-1
15.5 python311-aiohttp 3.9.3-150400.10.27.1 SUSE-SU-2024:4077-1
15.6 python3-aiohttp 3.6.0-150100.3.18.1 SUSE-SU-2024:4110-1
15.6 python311-aiohttp 3.9.3-150400.10.27.1 SUSE-SU-2024:4077-1

chainguard 1 release · 8 packages

fixed 8
py3-13-scanner-test-libraries-aiohttp kserve py3-cassandra-medusa airflow dask-gateway awx +2
chainguard fixes for CVE-2024-52304
ReleasePackageFixed in
py3-13-scanner-test-libraries-aiohttp 0.0.1-r3
kserve 0.14.0-r0
py3-cassandra-medusa +1 0.22.3-r1
airflow 2.10.3-r2
dask-gateway 2024.1.0-r11
awx 24.6.1-r2

2 more rows

debian 4 releases · 1 package

fixed 4
python-aiohttp
debian fixes for CVE-2024-52304
ReleasePackageFixed in
11 python-aiohttp 3.7.4-1+deb11u1
12 python-aiohttp 3.8.4-1+deb12u1
13 python-aiohttp 3.10.11-1
14 python-aiohttp 3.10.11-1

echo 1 release · 1 package

fixed 1
python-aiohttp
echo fixes for CVE-2024-52304
ReleasePackageFixed in
python-aiohttp 3.8.4-1+deb12u1

ubuntu 4 releases · 1 package

fixed 2 affected 2
python-aiohttp
ubuntu fixes for CVE-2024-52304
ReleasePackageFixed in
18.04-ESM python-aiohttp 3.0.1-1ubuntu0.1~esm5
20.04-ESM python-aiohttp 3.6.2-1ubuntu1+esm4
22.04 python-aiohttp affected
24.04 python-aiohttp affected

wolfi 1 release · 6 packages

fixed 6
kserve py3-cassandra-medusa airflow dask-gateway py3-aiohttp checkov
wolfi fixes for CVE-2024-52304
ReleasePackageFixed in
kserve 0.14.0-r0
py3-cassandra-medusa 0.22.3-r1
airflow 2.10.3-r2
dask-gateway 2024.1.0-r11
py3-aiohttp 3.10.11-r0
checkov 3.2.432-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.