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

Exp

aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. 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. Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling. The unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities. This vulnerability exists due to an incomplete fix for CVE-2023-47627. Version 3.9.2 fixes this vulnerability.

Published: 2024-01-29 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-23829 is rated High Exploit Risk (64.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.49%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-23829

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-23829

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-28 0.35% 0.49% +0.13%
2 2026-05-23 0.52% 0.35% -0.16%
3 2026-02-16 — 0.52% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-23829

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 2.5 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 2.5 [email protected]

Weakness enumeration for CVE-2024-23829

GitHub Security Advisory for CVE-2024-23829

GHSA-8qpw-xqxj-h4r2 · Severity: medium · Ecosystem: pip — aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators

OS Trackers for CVE-2024-23829

vendor priority summary link
alpine medium CVE-2024-23829: 1 source package rows (py3-aiohttp); 4 state rows across 4 repos (3.20-community, 3.21-community, 3.22-community, edge-community); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2024-23829
debian not yet assigned CVE-2024-23829 not yet assigned priority: Debian including 1 source packages (python-aiohttp), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-23829
redhat medium — https://access.redhat.com/security/cve/CVE-2024-23829
suse medium CVE-2024-23829 severity moderate: SUSE including 7 source package names (python-aiohttp, python-aiohttp-doc, …), 80 product×package rows across 67 product lines (Image SLES15-SP4-BYOS-Azure, Image SLES15-SP4-HPC-BYOS-Azure, … (67 product lines)): Fixed 60, Will Not Fix 20. https://www.suse.com/security/cve/CVE-2024-23829/
ubuntu medium CVE-2024-23829 medium priority: Ubuntu including 1 source packages (python-aiohttp), 11 status rows across 11 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 4, released 4, ignored 2, DNE 1. https://ubuntu.com/security/CVE-2024-23829

Affected software / configurations for CVE-2024-23829

Vendor Product Version Raw CPE
aiohttp aiohttp < 3.9.2 cpe:2.3:a:aiohttp:aiohttp:*:*:*:*:*:*:*:*
fedoraproject fedora 39 cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*

References for CVE-2024-23829

cvelogic Threat Intelligence