python-aiohttp - Debian Package Tracker

general

source: python-aiohttp (main)
version: 3.10.11-1
maintainer: Debian Python Team (DMD)
uploaders: Paul Tagliamonte [DMD] – Tianon Gravi [DMD] – William Grzybowski [DMD] – Piotr Ożarowski [DMD]
arch: all any
std-ver: 4.7.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 3.5.1-1+deb10u1
o-o-sec: 3.5.1-1+deb10u1
oldstable: 3.7.4-1
stable: 3.8.4-1+deb12u1
stable-sec: 3.8.4-1+deb12u1
testing: 3.10.11-1
unstable: 3.10.11-1

versioned links

3.5.1-1+deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.7.4-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.8.4-1+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.10.11-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

python-aiohttp-doc
python3-aiohttp (1 bugs: 0, 1, 0, 0)

action needed

A new upstream version is available: 3.11.11 high

A new upstream version 3.11.11 is available, you should consider packaging it.

Created: 2024-11-14 Last update: 2025-01-21 00:04

10 security issues in bullseye high

There are 10 open security issues in bullseye.

3 important issues:

CVE-2024-30251: aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. In affected versions an attacker can send a specially crafted POST (multipart/form-data) request. When the aiohttp server processes it, the server will enter an infinite loop and be unable to process any further requests. An attacker can stop the application from serving requests after sending a single request. This issue has been addressed in version 3.9.4. Users are advised to upgrade. Users unable to upgrade may manually apply a patch to their systems. Please see the linked GHSA for instructions.
CVE-2024-42367: 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.
CVE-2024-52304: aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.10.11, the Python parser parses newlines in chunk extensions incorrectly which can lead to request smuggling vulnerabilities under certain conditions. If a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or `AIOHTTP_NO_EXTENSIONS` is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections. Version 3.10.11 fixes the issue.

7 issues postponed or untriaged:

CVE-2023-47627: (needs triaging) aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. The HTTP parser in AIOHTTP has numerous problems with header parsing, which could lead to request smuggling. This parser is only used when AIOHTTP_NO_EXTENSIONS is enabled (or not using a prebuilt wheel). These bugs have been addressed in commit `d5c12ba89` which has been included in release version 3.8.6. Users are advised to upgrade. There are no known workarounds for these issues.
CVE-2023-47641: (needs triaging) aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Affected versions of aiohttp have a security vulnerability regarding the inconsistent interpretation of the http protocol. HTTP/1.1 is a persistent protocol, if both Content-Length(CL) and Transfer-Encoding(TE) header values are present it can lead to incorrect interpretation of two entities that parse the HTTP and we can poison other sockets with this incorrect interpretation. A possible Proof-of-Concept (POC) would be a configuration with a reverse proxy(frontend) that accepts both CL and TE headers and aiohttp as backend. As aiohttp parses anything with chunked, we can pass a chunked123 as TE, the frontend entity will ignore this header and will parse Content-Length. The impact of this vulnerability is that it is possible to bypass any proxy rule, poisoning sockets to other users like passing Authentication Headers, also if it is present an Open Redirect an attacker could combine it to redirect random users to another website and log the request. This vulnerability has been addressed in release 3.8.0 of aiohttp. Users are advised to upgrade. There are no known workarounds for this vulnerability.
CVE-2023-49081: (needs triaging) aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Improper validation made it possible for an attacker to modify the HTTP request (e.g. to insert a new header) or create a new HTTP request if the attacker controls the HTTP version. The vulnerability only occurs if the attacker can control the HTTP version of the request. This issue has been patched in version 3.9.0.
CVE-2023-49082: (needs triaging) aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Improper validation makes it possible for an attacker to modify the HTTP request (e.g. insert a new header) or even create a new HTTP request if the attacker controls the HTTP method. The vulnerability occurs only if the attacker can control the HTTP method (GET, POST etc.) of the request. If the attacker can control the HTTP version of the request it will be able to modify the request (request smuggling). This issue has been patched in version 3.9.0.
CVE-2024-23334: (needs triaging) 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 'follow_symlinks' can be used to determine whether to follow symbolic links outside the static root directory. When 'follow_symlinks' 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.
CVE-2024-23829: (needs triaging) aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Security-sensitive parts of the Python HTTP parser retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input. Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling. The unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities. This vulnerability exists due to an incomplete fix for CVE-2023-47627. Version 3.9.2 fixes this vulnerability.
CVE-2024-27306: (needs triaging) aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. A XSS vulnerability exists on index pages for static file handling. This vulnerability is fixed in 3.9.4. We have always recommended using a reverse proxy server (e.g. nginx) for serving static files. Users following the recommendation are unaffected. Other users can disable `show_index` if unable to upgrade.

Created: 2023-07-21 Last update: 2025-01-17 04:00

Depends on packages which need a new maintainer normal

The packages that python-aiohttp depends on which need a new maintainer are:

aiodns (#1074759)
- Recommends: python3-aiodns
- Build-Depends: python3-aiodns

Created: 2024-07-02 Last update: 2025-01-21 03:30

1 new commit since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 14cde11782fdd9da9d21789af90e5e95174ded0c
Author: Colin Watson <cjwatson@debian.org>
Date:   Mon Dec 30 09:58:46 2024 +0000

    Retroactively record fix for CVE-2024-52304

Created: 2024-12-30 Last update: 2025-01-17 07:32

4 low-priority security issues in bookworm low

There are 4 open security issues in bookworm.

1 issue left for the package maintainer to handle:

CVE-2024-42367: (needs triaging) 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.

You can find information about how to handle this issue in the security team's documentation.

3 ignored issues:

CVE-2023-37276: aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. aiohttp v3.8.4 and earlier are bundled with llhttp v6.0.6. Vulnerable code is used by aiohttp for its HTTP request parser when available which is the default case when installing from a wheel. This vulnerability only affects users of aiohttp as an HTTP server (ie `aiohttp.Application`), you are not affected by this vulnerability if you are using aiohttp as an HTTP client library (ie `aiohttp.ClientSession`). Sending a crafted HTTP request will cause the server to misinterpret one of the HTTP header values leading to HTTP request smuggling. This issue has been addressed in version 3.8.5. Users are advised to upgrade. Users unable to upgrade can reinstall aiohttp using `AIOHTTP_NO_EXTENSIONS=1` as an environment variable to disable the llhttp HTTP request parser implementation. The pure Python implementation isn't vulnerable.
CVE-2024-23829: aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Security-sensitive parts of the Python HTTP parser retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input. Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling. The unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities. This vulnerability exists due to an incomplete fix for CVE-2023-47627. Version 3.9.2 fixes this vulnerability.
CVE-2024-27306: aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. A XSS vulnerability exists on index pages for static file handling. This vulnerability is fixed in 3.9.4. We have always recommended using a reverse proxy server (e.g. nginx) for serving static files. Users following the recommendation are unaffected. Other users can disable `show_index` if unable to upgrade.

Created: 2023-07-21 Last update: 2025-01-17 04:00

debian/patches: 5 patches to forward upstream low

Among the 5 debian patches available in version 3.10.11-1 of the package, we noticed the following issues:

5 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2024-12-30 07:00

testing migrations

This package is part of the ongoing testing transition known as auto-upperlimit-python3. Please avoid uploads unrelated to this transition, they would likely delay it and require supplementary work from the release managers. On the other hand, if your package has problems preventing it to migrate to testing, please fix them as soon as possible. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[2025-01-17] python-aiohttp 3.10.11-1 MIGRATED to testing (Debian testing watch)
[2024-12-30] Accepted python-aiohttp 3.10.11-1 (source) into unstable (Colin Watson)
[2024-12-12] Accepted python-aiohttp 3.8.4-1+deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2024-12-11] Accepted python-aiohttp 3.8.4-1+deb12u1 (source) into stable-security (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2024-11-19] python-aiohttp 3.10.10-2 MIGRATED to testing (Debian testing watch)
[2024-11-13] Accepted python-aiohttp 3.10.10-2 (source) into unstable (Colin Watson)
[2024-10-29] Accepted python-aiohttp 3.10.10-1 (source) into unstable (Piotr Ożarowski)
[2024-10-01] Accepted python-aiohttp 3.10.8-1 (source) into unstable (Piotr Ożarowski)
[2024-09-27] Accepted python-aiohttp 3.10.6-1 (source) into unstable (Piotr Ożarowski)
[2024-08-29] python-aiohttp 3.10.5-1 MIGRATED to testing (Debian testing watch)
[2024-08-24] Accepted python-aiohttp 3.10.5-1 (source) into unstable (Piotr Ożarowski)
[2024-08-19] Accepted python-aiohttp 3.10.4-1 (source) into unstable (Colin Watson)
[2024-08-18] Accepted python-aiohttp 3.10.3-3 (source) into unstable (Colin Watson)
[2024-08-15] Accepted python-aiohttp 3.10.3-2 (source) into unstable (Colin Watson)
[2024-08-14] Accepted python-aiohttp 3.10.3-1 (source) into experimental (Colin Watson)
[2024-08-05] Accepted python-aiohttp 3.10.1-1 (source) into experimental (Colin Watson)
[2024-08-04] Accepted python-aiohttp 3.10.0-1 (source) into experimental (Colin Watson)
[2024-06-21] python-aiohttp 3.9.5-1 MIGRATED to testing (Debian testing watch)
[2024-06-16] Accepted python-aiohttp 3.9.5-1 (source) into unstable (Colin Watson)
[2023-12-21] python-aiohttp 3.9.1-1 MIGRATED to testing (Debian testing watch)
[2023-12-14] Accepted python-aiohttp 3.9.1-1 (source) into unstable (Bo YU) (signed by: bage@debian.org)
[2023-10-19] python-aiohttp 3.8.6-1 MIGRATED to testing (Debian testing watch)
[2023-10-14] Accepted python-aiohttp 3.8.6-1 (source) into unstable (Piotr Ożarowski)
[2023-08-25] python-aiohttp 3.8.5-1 MIGRATED to testing (Debian testing watch)
[2023-08-20] Accepted python-aiohttp 3.8.5-1 (source) into unstable (Piotr Ożarowski)
[2023-02-26] python-aiohttp 3.8.4-1 MIGRATED to testing (Debian testing watch)
[2023-02-16] Accepted python-aiohttp 3.8.4-1 (source) into unstable (Piotr Ożarowski)
[2022-11-05] python-aiohttp 3.8.3-1 MIGRATED to testing (Debian testing watch)
[2022-10-31] Accepted python-aiohttp 3.8.3-1 (source) into unstable (Piotr Ożarowski)
[2022-10-19] python-aiohttp 3.8.1-5 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 2
RC: 0
I&N: 1
M&W: 0
F&P: 1
patch: 0

links

homepage
lintian
buildd: logs, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.10.11-1
1 bug