Jnovikov

**Name of the Vulnerable Software and Affected Versions** aiohttp versions prior to 3.9.0 **Description** The issue is related to improper validation in the aiohttp HTTP client/server framework, allowing an attacker to modify the HTTP request or create a new one if they control the HTTP method. This can lead to HTTP request smuggling if the attacker can control the HTTP version of the request. The vulnerability occurs when an attacker can control the HTTP method of the request, such as GET or POST. **Recommendations** For versions prior to 3.9.0, update to version 3.9.0 to resolve the issue. As a temporary workaround, consider performing manual validation of user-provided values for the request method, such as restricting it to known values like GET or POST.

**Name of the Vulnerable Software and Affected Versions** aiohttp versions prior to 3.9.0 **Description** The issue arises from improper validation, allowing an attacker to modify the HTTP request or create a new one if they control the HTTP version. This can lead to CRLF injection and Request Smuggling. The vulnerability is exploitable when the attacker can control the HTTP version of the request, including its type, and when the `Connection` header is passed to the `headers` parameter. For example, if an unvalidated JSON value is used as a version and the attacker passes an array as the `version` parameter, it can bypass validation. **Recommendations** For versions prior to 3.9.0, update to version 3.9.0 to resolve the issue. As a temporary workaround, validate the user input to the `version` parameter to ensure it is a `str`.

**Name of the Vulnerable Software and Affected Versions** onnx versions prior to 1.13.0 **Description** The issue allows Directory Traversal, where the `external data` field of the tensor proto can contain a path to a file outside the model's current directory or user-provided directory. For example, an attacker could use a path like "../../../etc/passwd". **Recommendations** For versions prior to 1.13.0, update to version 1.13.0 or later to resolve the issue. As a temporary workaround, consider restricting access to sensitive files and directories to minimize the risk of exploitation.