https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 08:56:05 +0000 https://vulnerability.circl.lu/vuln/cve-2024-23334 <p><strong>Affected:</strong> aio-libs aiohttp</p> <p>aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option &#39;follow_symlinks&#39; can be used to determine whether to follow symbolic links outside the static root directory. When &#39;follow_symlinks&#39; is set to True, there is no validation to check if reading a file is within the root directory. This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present. Disabling follow_symlinks and using a reverse proxy are encouraged mitigations. Version 3.9.2 fixes this issue.</p> <p><strong>Affected:</strong> aio-libs aiohttp</p> <p>aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option &#39;follow_symlinks&#39; can be used to determine whether to follow symbolic links outside the static root directory. When &#39;follow_symlinks&#39; is set to True, there is no validation to check if reading a file is within the root directory. This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present. Disabling follow_symlinks and using a reverse proxy are encouraged mitigations. Version 3.9.2 fixes this issue.</p> https://vulnerability.circl.lu/vuln/cve-2024-23334 https://vulnerability.circl.lu/vuln/ghsa-5h86-8mv2-jq9f <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>### Summary Improperly configuring static resource resolution in aiohttp when used as a web server can result in the unauthorized reading of arbitrary files on the system.</p> <p>### Details When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option &#39;follow_symlinks&#39; can be used to determine whether to follow symbolic links outside the static root directory. When &#39;follow_symlinks&#39; is set to True, there is no validation to check if a given file path is within the root directory.This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present.</p> <p>i.e. An application is only vulnerable with setup code like: ``` app.router.add_routes([ web.static(&#34;/static&#34;, &#34;static/&#34;, follow_symlinks=True), # Remove follow_symlinks to avoid the vulnerability ]) ```</p> <p>### Impact This is a directory traversal vulnerability with CWE ID 22. When using aiohttp as a web server and enabling static resource resolution with `follow_symlinks` set to True, it can lead to this vulnerability. This vulnerability has been present since the introduction of the `follow_symlinks` parameter.</p> <p>### Workaround Even if upgrading to a patched version of aiohttp, we recommend following these steps regardless.</p> <p>If using `follow_symlinks=True` outside of a restricted local development environment, disable the option immediately. This option is NOT…</p> <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>### Summary Improperly configuring static resource resolution in aiohttp when used as a web server can result in the unauthorized reading of arbitrary files on the system.</p> <p>### Details When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option &#39;follow_symlinks&#39; can be used to determine whether to follow symbolic links outside the static root directory. When &#39;follow_symlinks&#39; is set to True, there is no validation to check if a given file path is within the root directory.This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present.</p> <p>i.e. An application is only vulnerable with setup code like: ``` app.router.add_routes([ web.static(&#34;/static&#34;, &#34;static/&#34;, follow_symlinks=True), # Remove follow_symlinks to avoid the vulnerability ]) ```</p> <p>### Impact This is a directory traversal vulnerability with CWE ID 22. When using aiohttp as a web server and enabling static resource resolution with `follow_symlinks` set to True, it can lead to this vulnerability. This vulnerability has been present since the introduction of the `follow_symlinks` parameter.</p> <p>### Workaround Even if upgrading to a patched version of aiohttp, we recommend following these steps regardless.</p> <p>If using `follow_symlinks=True` outside of a restricted local development environment, disable the option immediately. This option is NOT…</p> https://vulnerability.circl.lu/vuln/ghsa-5h86-8mv2-jq9f https://vulnerability.circl.lu/vuln/pysec-2024-24 <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option &#39;follow_symlinks&#39; can be used to determine whether to follow symbolic links outside the static root directory. When &#39;follow_symlinks&#39; is set to True, there is no validation to check if reading a file is within the root directory. This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present. Disabling follow_symlinks and using a reverse proxy are encouraged mitigations. Version 3.9.2 fixes this issue.</p> <p><strong>Affected:</strong> PyPI: aiohttp</p> <p>aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option &#39;follow_symlinks&#39; can be used to determine whether to follow symbolic links outside the static root directory. When &#39;follow_symlinks&#39; is set to True, there is no validation to check if reading a file is within the root directory. This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present. Disabling follow_symlinks and using a reverse proxy are encouraged mitigations. Version 3.9.2 fixes this issue.</p> https://vulnerability.circl.lu/vuln/pysec-2024-24