aio-libs aiohttp up to 3.10.1 symlink

Summaryinfo

A vulnerability described as critical has been identified in aio-libs aiohttp up to 3.10.1. This vulnerability affects unknown code. Executing a manipulation can lead to symlink. This vulnerability is registered as CVE-2024-42367. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in aio-libs aiohttp up to 3.10.1 and classified as critical. This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a symlink vulnerability. The CWE definition for the vulnerability is CWE-61. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.10.2, static routes which contain files with compressed variants (`.gz` or `.br` extension) are vulnerable to path traversal outside the root directory if those variants are symbolic links. The server protects static routes from path traversal outside the root directory when `follow_symlinks=False` (default). It does this by resolving the requested URL to an absolute path and then checking that path relative to the root. However, these checks are not performed when looking for compressed variants in the `FileResponse` class, and symbolic links are then automatically followed when performing the `Path.stat()` and `Path.open()` to send the file. Version 3.10.2 contains a patch for the issue.

The advisory is available at github.com. This vulnerability was named CVE-2024-42367 since 07/30/2024. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.

Upgrading to version 3.10.2 eliminates this vulnerability. Applying the patch ce2e9758814527589b10759a20783fb03b98339f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-2609). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• aio-libs

Name

• aiohttp

Version

• 3.10.0
• 3.10.1

License

• open-source

Website

• Product: https://github.com/aio-libs/aiohttp/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion