Update dependency aiohttp to v3.10.11 [SECURITY] - autoclosed #132
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==3.10.10
->==3.10.11
GitHub Vulnerability Alerts
CVE-2024-52303
Summary
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 eachMatchInfoError
producing a unique cache entry.Impact
If the user is making use of any middlewares with
aiohttp.web
then it is advisable to upgrade immediately.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.
Patch: aio-libs/aiohttp@bc15db6
CVE-2024-52304
Summary
The Python parser parses newlines in chunk extensions incorrectly which can lead to request smuggling vulnerabilities under certain conditions.
Impact
If a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or
AIOHTTP_NO_EXTENSIONS
is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections.Patch: aio-libs/aiohttp@259edc3
aiohttp has a memory leak when middleware is enabled when requesting a resource with a non-allowed method
CVE-2024-52303 / GHSA-27mf-ghqm-j3j8
More information
Details
Summary
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 eachMatchInfoError
producing a unique cache entry.Impact
If the user is making use of any middlewares with
aiohttp.web
then it is advisable to upgrade immediately.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.
Patch: aio-libs/aiohttp@bc15db6
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
aiohttp allows request smuggling due to incorrect parsing of chunk extensions
CVE-2024-52304 / GHSA-8495-4g3g-x7pr
More information
Details
Summary
The Python parser parses newlines in chunk extensions incorrectly which can lead to request smuggling vulnerabilities under certain conditions.
Impact
If a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or
AIOHTTP_NO_EXTENSIONS
is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections.Patch: aio-libs/aiohttp@259edc3
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aio-libs/aiohttp (aiohttp)
v3.10.11
Compare Source
====================
Bug fixes
Authentication provided by a redirect now takes precedence over provided
auth
when making requests with the client -- by :user:PLPeeters
.Related issues and pull requests on GitHub:
:issue:
9436
.Fixed :py:meth:
WebSocketResponse.close() <aiohttp.web.WebSocketResponse.close>
to discard non-close messages within its timeout window after sending close -- by :user:lenard-mosys
.Related issues and pull requests on GitHub:
:issue:
9506
.Fixed a deadlock that could occur while attempting to get a new connection slot after a timeout -- by :user:
bdraco
.The connector was not cancellation-safe.
Related issues and pull requests on GitHub:
:issue:
9670
, :issue:9671
.Fixed the WebSocket flow control calculation undercounting with multi-byte data -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
9686
.Fixed incorrect parsing of chunk extensions with the pure Python parser -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
9851
.Fixed system routes polluting the middleware cache -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
9852
.Removals and backward incompatible breaking changes
Improved performance of the connector when a connection can be reused -- by :user:
bdraco
.If
BaseConnector.connect
has been subclassed and replaced with custom logic, theceil_timeout
must be added.Related issues and pull requests on GitHub:
:issue:
9600
.Miscellaneous internal changes
Improved performance of the client request lifecycle when there are no cookies -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
9470
.Improved performance of sending client requests when the writer can finish synchronously -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
9485
.Improved performance of serializing HTTP headers -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
9603
.Passing
enable_cleanup_closed
to :py:class:aiohttp.TCPConnector
is now ignored on Python 3.12.7+ and 3.13.1+ since the underlying bug that caused asyncio to leak SSL connections has been fixed upstream -- by :user:bdraco
.Related issues and pull requests on GitHub:
:issue:
9726
, :issue:9736
.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.