CVE-2024-30251: Denial of service when trying to parse malformed POST requests in aiohttp
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 65.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: aio-libs aiohttp 3.9.4.
Low priority for now. Upgrade to aio-libs aiohttp 3.9.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. In affected versions an attacker can send a specially crafted POST (multipart/form-data) request. When the aiohttp server processes it, the server will enter an infinite loop and be unable to process any further requests. An attacker can stop the application from serving requests after sending a single request. This issue has been addressed in version 3.9.4. Users are advised to upgrade. Users unable to upgrade may manually apply a patch to their systems. Please see the linked GHSA for instructions.
- Published
- May 2, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- CWE-835
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| aiohttp | aiohttp | cpe:2.3:a:aiohttp:aiohttp |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
aio-libs aiohttp
- < 3.9.4affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- aiohttp aiohttpbefore 3.9.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | python-aiohttp | before 3.7.4-1+deb11u1 | 3.7.4-1+deb11u1 |
| Debian:12 | python-aiohttp | before 3.8.4-1+deb12u1 | 3.8.4-1+deb12u1 |
| Debian:13 | python-aiohttp | before 3.9.5-1 | 3.9.5-1 |
| openSUSE:Leap 15.5 | python-aiohttp | before 3.9.3-150400.10.30.1 | 3.9.3-150400.10.30.1 |
| openSUSE:Leap 15.5 | python-aiohttp | before 3.6.0-150100.3.21.1 | 3.6.0-150100.3.21.1 |
| PyPI | aiohttp | before 3.9.4 | 3.9.4 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-black | before 0:22.8.0-2.el8ap | 0:22.8.0-2.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-cryptography | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-cryptography-debuginfo | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-idna | before 0:3.7-1.el8ap | 0:3.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-jinja2 | before 0:3.1.4-1.el8ap | 0:3.1.4-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-requests | before 0:2.32.2-1.el8ap | 0:2.32.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-black | before 0:22.8.0-2.el8ap | 0:22.8.0-2.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-cryptography | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-cryptography-debugsource | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-idna | before 0:3.7-1.el8ap | 0:3.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-jinja2 | before 0:3.1.4-1.el8ap | 0:3.1.4-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-requests | before 0:2.32.2-1.el8ap | 0:2.32.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptor | before 0:1.4.8-1.el8ap | 0:1.4.8-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptorctl | before 0:1.4.8-1.el8ap | 0:1.4.8-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-black | before 0:22.8.0-2.el9ap | 0:22.8.0-2.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-cryptography | before 0:42.0.5-1.el9ap | 0:42.0.5-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-cryptography-debugsource | before 0:42.0.5-1.el9ap | 0:42.0.5-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-idna | before 0:3.7-1.el9ap | 0:3.7-1.el9ap |
+74
Same product
aiohttp: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-23334aiohttp.web.static(follow_symlinks=True) is vulnerable to directory traversal53Plan
- CVE-2024-52303aiohttp memory leak when middleware is enabled when requesting a resource with a non-allowed method34Monitor
- CVE-2025-69223AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-23829Jan 29, 2024 · aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators26Monitor
- ← EarlierCVE-2024-27306Apr 18, 2024 · aiohttp vulnerable to XSS on index pages for static file handling24Monitor
- Later →CVE-2024-42367Aug 12, 2024 · In aiohttp, compressed files as symlinks are not protected from path traversal19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| aio-libs aiohttp | 3.9.4 · description | Vendor (CNA) |
| debian:python-aiohttp | 3.8.4-1+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:python-aiohttp | 3.9.3-150400.10.30.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| PyPI:aiohttp | 3.9.4 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.7-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python-cryptography | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python-cryptography-debugsource | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography-debuginfo | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python39-cryptography | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-cryptography-debuginfo | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-pillow | 0:10.3.0-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography-debugsource | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptor | 0:1.4.8-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptorctl | 0:1.4.8-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| suse:python-aiohttp | 3.9.3-150400.10.30.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/aio-libs/aiohttp/commit/7eecdff163ccf029fbb1ddc9de4169d4aaeb6597
- github.com/aio-libs/aiohttp/commit/cebe526b9c34dc3a3da9140409db63014bc4cf19
- github.com/aio-libs/aiohttp/commit/f21c6f2ca512a026ce7f0f6c6311f62d6a638866
- github.com/aio-libs/aiohttp/security/advisories/GHSA-5m98-qgg9-wh84
- lists.debian.org/debian-lts-announce/2025/02/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.