aiohttp@3.1.0 vulnerabilities
Async http client/server framework (asyncio)
-
latest version
3.11.7
-
latest non vulnerable version
-
first published
11 years ago
-
latest version published
a day ago
-
licenses detected
- [0.10.0,)
Direct Vulnerabilities
Known vulnerabilities in the aiohttp package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
Affected versions of this package are vulnerable to HTTP Request Smuggling due to incorrect parsing of newlines in chunk extensions via the Note: Exploiting this vulnerability is possible when a pure Python version of aiohttp is installed (Without the usual C extensions) or How to fix HTTP Request Smuggling? Upgrade |
[,3.10.11)
|
Affected versions of this package are vulnerable to UNIX Symbolic Link (Symlink) Following through the Note This vulnerability impacts servers with static routes that contain compressed variants as symbolic links pointing outside the root directory or that permit users to upload or create such links. How to fix UNIX Symbolic Link (Symlink) Following? Upgrade |
[,3.10.2)
|
Affected versions of this package are vulnerable to Infinite loop when processing a How to fix Infinite loop? Upgrade |
[,3.9.4)
|
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) due to improper handling of index pages for static file serving when Note: This is only exploitable if the server is configured to allow users to upload files to the static directory and How to fix Cross-site Scripting (XSS)? Upgrade |
[,3.9.4)
|
Affected versions of this package are vulnerable to HTTP Request Smuggling due to improper validation of HTTP request elements. An attacker can potentially inject additional requests or cause unhandled exceptions leading to excessive resource consumption by exploiting leniencies in the HTTP parser and inconsistencies in error handling. How to fix HTTP Request Smuggling? Upgrade |
[,3.9.2)
|
Affected versions of this package are vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') via the configuration of static routes when the Notes: This vulnerability has been present since the introduction of the An application is only vulnerable with setup code like:
How to fix Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')? Upgrade |
[1.0.5,3.9.2)
|
Affected versions of this package are vulnerable to Improper Input Validation via the Note: This is only exploitable if the attacker can control the HTTP method of the request. How to fix Improper Input Validation? Upgrade |
[,3.9.0)
|
Affected versions of this package are vulnerable to Improper Input Validation in the ClientSession. An attacker can modify the Note: The vulnerability only occurs if the attacker can control the HTTP version of the request (including its type). How to fix Improper Input Validation? Upgrade |
[,3.9.0)
|
Affected versions of this package are vulnerable to HTTP Request Smuggling due to a vulnerable dependency. An attacker can exploit request smuggling vulnerabilities. How to fix HTTP Request Smuggling? Upgrade |
[,3.8.6)
|
Affected versions of this package are vulnerable to Inconsistent Interpretation of HTTP Messages due to the inconsistent interpretation of Note: This is only exploitable if a configuration with a reverse proxy that accepts both Additionally, if an Open Redirect is present, it can be combined to redirect random users to an attacker's website and log the request. How to fix Inconsistent Interpretation of HTTP Messages? Upgrade |
[,3.8.0)
|
Affected versions of this package are vulnerable to HTTP Request Smuggling via the HTTP parser. An attacker can manipulate the header parsing, leading to potential request smuggling by exploiting the incorrect usage of the Note: This is only exploitable if How to fix HTTP Request Smuggling? Upgrade |
[,3.8.6)
|
Affected versions of this package are vulnerable to HTTP Request Smuggling in that Note This vulnerability only affects users of How to fix HTTP Request Smuggling? Upgrade |
[,3.8.5)
|
Affected versions of this package are vulnerable to HTTP Header Injection since aiohttp simply concatenated headers without any validation. This allowed an attacker to inject arbitrary content into the headers, including CRLF characters. PoC
How to fix HTTP Header Injection? Upgrade |
[,3.8.0)
|
Affected versions of this package are vulnerable to Open Redirect. Redirects are possible within the How to fix Open Redirect? Upgrade |
[,3.7.4)
|