3.14.3
12 years ago
2 months ago
Known vulnerabilities in the aiohttp package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
Affected versions of this package are vulnerable to HTTP Request Smuggling in the WebSocket upgrade. An attacker can bypass request boundaries and interfere with HTTP request processing by crafting specially constructed HTTP requests. How to fix HTTP Request Smuggling? Upgrade | [,3.14.2) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the WebSocket client. An attacker can cause unexpected decompression of WebSocket frames by sending frames with the RSV1 bit set without proper negotiation, potentially leading to increased CPU or memory consumption. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.14.2) |
Affected versions of this package are vulnerable to Use After Free in the C HTTP response parser error handling. An attacker can cause the application to crash or become unresponsive by sending a specially crafted malformed chunked response. How to fix Use After Free? Upgrade | [,3.14.3) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the handling of HTTP/1 pipelined requests queue without a limit. An attacker can exhaust system memory by sending a large number of pipelined requests, potentially causing service disruption. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.14.1) |
Affected versions of this package are vulnerable to Improper Resource Shutdown or Release in the payload response resources when a client disconnects during a write operation. An attacker can cause temporary resource exhaustion by repeatedly initiating connections and disconnecting mid-transfer, leading to open files or similar resources not being released until garbage collection occurs. How to fix Improper Resource Shutdown or Release? Upgrade | [,3.14.1) |
Affected versions of this package are vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) during cleanup. An attacker can exhaust system memory by sending a specially crafted compressed payload that is decompressed into memory in a single chunk. How to fix Improper Handling of Highly Compressed Data (Data Amplification)? Upgrade | [,3.14.1) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.14.1) |
Affected versions of this package are vulnerable to Improper Validation of Certificate with Host Mismatch in the How to fix Improper Validation of Certificate with Host Mismatch? Upgrade | [,3.14.1) |
Affected versions of this package are vulnerable to Exposure of Private Personal Information to an Unauthorized Actor in the How to fix Exposure of Private Personal Information to an Unauthorized Actor? Upgrade | [,3.14.1) |
Affected versions of this package are vulnerable to HTTP Response Splitting via Note: This is only exploitable if user-controlled strings are passed into the How to fix HTTP Response Splitting? Upgrade | [,3.14.0) |
Affected versions of this package are vulnerable to Insufficiently Protected Credentials via the Note: This is only exploitable if the client follows redirects to attacker-controlled domains. How to fix Insufficiently Protected Credentials? Upgrade | [,3.14.1) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.14.1) |
Affected versions of this package are vulnerable to Origin Validation Error via the How to fix Origin Validation Error? Upgrade | [,3.14.0) |
Affected versions of this package are vulnerable to Deserialization of Untrusted Data via the How to fix Deserialization of Untrusted Data? Upgrade | [,3.14.0) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to insufficient restrictions in the handling of HTTP headers and trailers. An attacker can exhaust system memory by sending specially crafted requests, potentially leading to service unavailability. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the static resource handler on Windows. An attacker can extract NTLMv2 credential hashes by accessing specially crafted remote paths, potentially leading to credential theft. How to fix Server-side Request Forgery (SSRF)? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to HTTP Response Splitting in the construction of multipart request headers when untrusted input is used for the How to fix HTTP Response Splitting? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to Information Exposure in the handling of cross-origin redirects, where How to fix Information Exposure? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to HTTP Request Smuggling via the processing of duplicate Note: This is only exploitable if a reverse proxy applies security rules based on the How to fix HTTP Request Smuggling? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the processing of multipart headers. An attacker can cause excessive memory consumption by sending a response with an unusually large number of multipart headers. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to HTTP Response Splitting via the How to fix HTTP Response Splitting? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to HTTP Response Splitting in the How to fix HTTP Response Splitting? Upgrade | [,3.13.4) |
Affected versions of this package are vulnerable to Logging of Excessive Data via the How to fix Logging of Excessive Data? Upgrade | [,3.13.3) |
Affected versions of this package are vulnerable to Infinite loop in the Note: This is only exploitable if Python optimizations are enabled (using the How to fix Infinite loop? Upgrade | [,3.13.3) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.13.3) |
Affected versions of this package are vulnerable to HTTP Request Smuggling via the parsing of Range headers. An attacker can potentially interfere with HTTP request processing by supplying non-ASCII decimals in the header, which may lead to unexpected parser mismatches. How to fix HTTP Request Smuggling? Upgrade | [,3.13.3) |
Affected versions of this package are vulnerable to Information Exposure over the How to fix Information Exposure? Upgrade | [,3.13.3) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.13.3) |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | [,3.13.3) |
Affected versions of this package are vulnerable to HTTP Request Smuggling via the unicode processing of HTTP header values. An attacker can bypass firewall or proxy protections by sending requests containing non-ASCII characters. Note: This is only exploitable if C extensions are not in use (pure python installation) or if the How to fix HTTP Request Smuggling? Upgrade | [,3.13.3) |
Affected versions of this package are vulnerable to HTTP Request Smuggling via incorrect parsing of the Note:
This is exploitable if the pure Python version of aiohttp is installed or the How to fix HTTP Request Smuggling? Upgrade | [,3.12.14) |
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) |