Approved changes feed: RSS · Atom
cpe:2.3:a:aiohttp:aio-libs:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Aiohttp (ad3b2e5d-9009-5da4-af40-9b5b019c6d88) |
|---|---|
| Product | Aio Libs (eece0e4d-6af3-58f4-be4f-029a908a8f5d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-52303 |
vulnerable | 2026-06-08 06:52:14.752429 |
aiohttp memory leak when middleware is enabled when requesting a resource with a non-allowed method
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.
Published: 2024-11-18T20:08:15.387Z
Updated: 2024-11-19T14:45:27.044Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.