fix: (upgrade) aiohttp allows request smuggling due to incorrect parsing of chunk extensions #70
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.
What changed? Why?
The parser parses newlines in chunk extensions incorrectly which can lead to request smuggling vulnerabilities under certain conditions. If a pure Python version of aiohttp is installed AIOHTTP_NO_EXTENSIONS is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections.
In specific setups, if the pure Python parser is in use, an attacker could craft a malicious HTTP request containing newlines within the chunk extension headers. This request could then be processed incorrectly, enabling a request smuggling attack.
Mitigation
To secure your systems, it is strongly recommended to update aiohttp to version 3.10.11 or later. You can find more details on the update in the following commit link.
CVE-2024-52304
WeaknessCWE-444