aiohttp memory leak when middleware is enabled when requesting a resource with a non-allowed method
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| aio-libs | aiohttp | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-3176 | aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. In versions starting with 3.10.6 and prior to 3.10.11, a memory leak can occur when a request produces a MatchInfoError. This was caused by adding an entry to a cache on each request, due to the building of each MatchInfoError producing a unique cache entry. An attacker may be able to exhaust the memory resources of a server by sending a substantial number (100,000s to millions) of such requests. Those who use any middlewares with aiohttp.web should upgrade to version 3.10.11 to receive a patch. |
Github GHSA |
GHSA-27mf-ghqm-j3j8 | aiohttp has a memory leak when middleware is enabled when requesting a resource with a non-allowed method |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.591% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aiohttp aiohttp
|
|
| CPEs | cpe:2.3:a:aiohttp:aiohttp:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aiohttp aiohttp
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aiohttp
Aiohttp aio-libs |
|
| CPEs | cpe:2.3:a:aiohttp:aio-libs:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aiohttp
Aiohttp aio-libs |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. In versions starting with 3.10.6 and prior to 3.10.11, a memory leak can occur when a request produces a MatchInfoError. This was caused by adding an entry to a cache on each request, due to the building of each MatchInfoError producing a unique cache entry. An attacker may be able to exhaust the memory resources of a server by sending a substantial number (100,000s to millions) of such requests. Those who use any middlewares with aiohttp.web should upgrade to version 3.10.11 to receive a patch. | |
| Title | aiohttp memory leak when middleware is enabled when requesting a resource with a non-allowed method | |
| Weaknesses | CWE-772 | |
| References |
| |
| Metrics |
cvssV4_0
|