AIOHTTP versions from 1.5.3 up to but not including 1.6.2 have a vulnerability where decompressing concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity. This can lead to event loop blocking on servers or clients when processing specially crafted compressed payloads. The issue is fixed in version 1.6.2.
A vulnerability in AIOHTTP's pure-Python parser causes the request buffer to grow excessively when an upgrade request is declined, leading to repeated processing of pipelined requests and excessive memory use. This affects versions from 1.5.3 up to but not including 1.6.2 when the Python parser is used instead of the default C parser. A patch is available in version 1.6.2.
AIOHTTP versions from 1.5.3 up to but not including 1.6.2 have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without limit until the upgrade handler completes. This can lead to unbounded memory consumption if an attacker streams large amounts of data behind the upgrade request.
AIOHTTP versions from 1.5.3 up to but not including 1.6.2 contain a vulnerability in the WebSocket max_msg_size check due to an integer overflow in the C extension. This flaw allows an attacker to bypass the maximum message size restriction by sending a crafted WebSocket message with a declared length near 2^63, causing unbounded memory usage. The issue is fixed in version 1.6.2. A workaround is to disable C extensions and use the Python reader by setting AIOHTTP_NO_EXTENSIONS=1 if upgrading is not possible.
AIOHTTP versions from 1.5.3 up to but not including 1.6.2 contain a vulnerability in multipart request handling where base64-encoded parts can bypass the configured client_max_size limit. This occurs because the multipart reader reads base64 chunks until their length is a multiple of 4 without enforcing size limits, allowing excessive memory consumption or event loop blocking. The issue is fixed in version 1.6.2.
AIOHTTP versions from 1.5.3 up to but not including 1.6.2 have a vulnerability where the Request.post() method does not limit the number of URL-encoded form fields. This can cause the event loop to be blocked due to quadratic time processing of repeated keys in a MultiDict. The issue is fixed in version 1.6.2.
AIOHTTP client CookieJar improperly handled Set-Cookie headers by creating additional cookies from unrecognized name=value attributes without limiting the number of stored cookies. This allowed a malicious server to cause excessive memory and CPU usage on the client by forcing it to store and send a very large number of cookies, especially on redirects, resulting in oversized Cookie headers.
AIOHTTP's Application.add_domain() method had a performance issue where using two or more wildcards in a domain mask caused polynomial-time matching delays on the event loop when processing long Host headers. This could be exploited by an attacker to stall the server. The issue affects versions from 1.5.3 up to but not including 1.6.2. A fix is available in version 1.6.2.
In the Aliro access control reference
applications of the Nordic Semiconductor nRF Door Lock and Access Control
Add-on v1.0.0 through v1.1.1, the stored Access Document record does not
retain validFrom and validUntil. The cached public key path (VerifyPublicKey())
and the Kpersistent fast path (_VerifyKPersistentKey()) therefore never
re-evaluate the Access Document validity period. An attacker who held a
time-limited Aliro credential that was valid when first presented can
continue to obtain physical access after the Access Document has expired, for
as long as the cached record remains available. Fixed in v1.2.0.
In the Aliro access control reference
applications of the Nordic Semiconductor nRF Door Lock and Access Control
Add-on v1.0.0 through v1.1.1, built with Credential Issuer CA
certificate-based issuer trust (CONFIG_DOOR_LOCK_CREDENTIAL_ISSUER_CA) and
the Aliro Step-up phase (CONFIG_DOOR_LOCK_STEP_UP_PHASE) enabled,
AccessManagerImpl::ProcessValidityIteration() treats a failed lookup of the
Credential Issuer in the provisioned issuer array as success. For an issuer
trusted through a certificate chain but not provisioned, the
ValidityIteration (credential-rollback) check is therefore skipped. A former
authorized holder with an old but correctly issuer-signed Access Document can
be granted physical access after the issuer has advanced its iteration to
revoke that credential. The default Matter provisioning configuration is not
affected. Fixed in v1.2.0.
A vulnerability in AIOHTTP's WebSocket implementation allows attackers to bypass receive queue limits by sending many small or compressed messages. This can cause excessive memory consumption on the server or client side. The issue arises because the WebSocket reader continues parsing frames after the receive queue pauses the transport, and empty messages are not counted towards the queue size. A fix is available in version 20250130_14.