CVE-2024-52304: aiohttp vulnerable to request smuggling due to incorrect parsing of chunk extensions

Published Nov 18, 2024
·
Updated

Summary The Python parser parses newlines in chunk extensions incorrectly which can lead to request smuggling vulnerabilities under certain conditions.

Impact If a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or AIOHTTPNOEXTENSIONS is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections.

-----

Patch: https://github.com/aio-libs/aiohttp/commit/259edc369075de63e6f3a4eaade058c62af0df71

Other sources

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 AIOHTTPNOEXTENSIONS 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.

NVD

Affected Software

2 affected componentsFixes available
pip/aiohttp<=3.10.10
3.10.11
aiohttp aiohttp<3.10.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/aiohttp to a version that resolves this vulnerability.

    Fixed in 3.10.11
  2. Upgrade

    Upgrade aiohttp to a version that resolves this vulnerability.

    Fixed in 3.10.11Patch 259edc369075de63e6f3a4eaade058c62af0df71
  3. Compensating control

    If a pure-Python aiohttp deployment is used (no C extensions) or `AIOHTTP_NO_EXTENSIONS` is enabled, apply compensating network controls to prevent request smuggling exploitation (e.g., strengthen/protect firewall or proxy protections) until aiohttp 3.10.11 is deployed.

Event History

Nov 18, 2024
CVE Published
via MITRE·08:12 PM
Data Sourced
via MITRE·08:12 PM
DescriptionWeakness
Data Sourced
via Red Hat·09:02 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·09:02 PM
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyAffected Software
Apr 13, 58390
Event
via NVD·06:54 PM

Frequently Asked Questions

1

What is the severity of CVE-2024-52304?

CVE-2024-52304 has been classified as a medium severity vulnerability due to its potential for causing request smuggling under specific conditions.

2

How do I fix CVE-2024-52304?

To fix CVE-2024-52304, upgrade aiohttp to version 3.10.11 or later.

3

What software is affected by CVE-2024-52304?

CVE-2024-52304 specifically affects aiohttp version 3.10.10 and earlier when using a pure Python installation.

4

What kind of vulnerabilities can CVE-2024-52304 lead to?

CVE-2024-52304 can lead to request smuggling vulnerabilities, potentially allowing attackers to bypass security measures.

5

Is CVE-2024-52304 reversible?

CVE-2024-52304 does not have a reversible condition, but implementing the recommended upgrade mitigates the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203