Server memory exhaustion via middleware cache pollution
Published Nov 18, 2024 · Updated Nov 19, 2024
Resource leak in aiohttp 3.10.6 through 3.10.10 allows remote attackers to exhaust server memory through repeated invalid-method requests. Application._handle passes each fresh SystemRoute handler from a MatchInfoError into an unbounded _build_middlewares LRU cache. The condition requires aiohttp.web middleware, and exploitation requires hundreds of thousands to millions of requests before service interruption.
Summary
What happened
Resource leak in aiohttp 3.10.6 through 3.10.10 allows remote attackers to exhaust server memory through repeated invalid-method requests. Application._handle passes each fresh SystemRoute handler from a MatchInfoError into an unbounded _build_middlewares LRU cache. The condition requires aiohttp.web middleware, and exploitation requires hundreds of thousands to millions of requests before service interruption.
The record
- CVE
- CVE-2024-52303
- Published
- Nov 18, 2024
- Updated
- Nov 19, 2024
- Vendor
- aio-libs
- Product
- aiohttp
- Classifications
- CWE-772, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 18, 2024CVE publishedPublication date reported by the CVE source.
- Nov 19, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.10.6, < 3.10.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo