AIOHTTP versions >=0.6.0 <0.7.0 and >=0.8.0 have a vulnerability where data received during an upgrade request (such as a WebSocket handshake) is buffered without limit until the handler completes. This can lead to unbounded memory usage if an attacker streams data behind the upgrade request to a handler that does not promptly accept or reject the upgrade. A fix is available in version 0.7.0.
AIOHTTP versions >=0.6.0 <0.7.0 and >=0.8.0 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 max_msg_size limit by sending a crafted WebSocket message with a declared length near 2^63, causing unbounded memory usage. The issue is fixed in version 0.7.0. A workaround is to disable C extensions by setting AIOHTTP_NO_EXTENSIONS=1 to use the unaffected Python reader.
A vulnerability in AIOHTTP's multipart handling allows an attacker to bypass the client_max_size limit by exploiting how base64-encoded multipart parts are read. Specifically, the BodyPartReader.read_chunk() method reads until the chunk length is a multiple of 4 without enforcing a byte limit, enabling excessive memory consumption or event loop blocking. This affects versions >=0.6.0 <0.7.0 and >=0.8.0 and is fixed in version 0.7.0.
AIOHTTP versions 0.6.0 up to but not including 0.7.0, and versions 0.8.0 are vulnerable to a denial-of-service condition where an attacker can block the event loop by sending a URL-encoded form POST request with a large number of repeated keys. This occurs because Request.post() had no limit on the number of fields, causing quadratic time complexity when processing repeated keys in a MultiDict. The vulnerability is fixed in version 0.7.0.
AIOHTTP's client CookieJar had a vulnerability where unrecognized Set-Cookie attributes caused additional cookies to be stored without limit. This allowed a malicious server to cause excessive memory and CPU usage on the client by making it store a very large number of cookies, resulting in oversized Cookie headers on subsequent requests. The issue was fixed in version 0.7.0.
AIOHTTP's Application.add_domain() function had a performance issue where using two or more wildcards (*) in a domain mask caused polynomial-time matching delays on long Host headers, leading to event loop stalls. This could be exploited by an attacker to stall the server by sending requests with long Host headers against such domain masks. The issue is fixed in version 0.7.0. A workaround is to use at most one wildcard in domain masks.
In nanobot, the WebSocket gateway allows a standard client holding a valid client token to select an existing directory outside the operator-configured workspace as the root of a new conversation. The agent can then read and expose files in that directory that are readable by the nanobot service account.
This issue affects nanobot (nanobot-ai) from 0.3.5 before 0.4.1.
In nanobot, when sandboxed exec is enabled, the shell executable used to run commands can be selected by the caller and is launched before the sandbox is applied. An attacker who can induce the agent to create an executable in the workspace and select it as the shell can cause that executable to run outside the sandbox (e.g. Linux bubblewrap), with the operating-system permissions of the nanobot process.
This issue affects nanobot (nanobot-ai) from 0.2.1 before 0.4.1.
In the Matter door lock applications of
the Nordic Semiconductor nRF Door Lock and Access Control Add-on v1.0.0
through v1.1.1, AccessManager::ValidateCredential() checks only credential
occupancy and the secret bytes, and never reads the owning user's UserStatus.
It also returns success when no owning user can be resolved. A user suspended
by setting their status to OccupiedDisabled can continue to unlock the door
with their previously assigned credential, and an orphaned but occupied
credential is also accepted. Fixed in v1.2.0.
In
the Matter and Aliro Door Lock Application of the Nordic Semiconductor nRF Door
Lock and Access Control Add-on v1.0.0 through v1.1.1 with
CONFIG_DOOR_LOCK_STEP_UP_PHASE enabled, deleting a Credential Issuer passes the
1-based Matter credential index to ClearValidityIterations(), which expects a
0-based storage index. The intended issuer's ValidityIteration state is left in
place, and the state of the adjacent, still-provisioned issuer is cleared. This
resets that issuer's rollback protection. An attacker holding an older but correctly
signed Access Document from the adjacent issuer, whose validity iteration had
been superseded, can then potentially obtain physical access. Fixed in v1.2.0.
AIOHTTP versions >=3.27.1_1 and <3.27.1_2 have a vulnerability in the WebSocket receive queue handling where small or compressed messages bypass queue limits, causing excessive memory use. This occurs because the WebSocket reader continues parsing frames after the receive queue pauses the transport, and empty messages are not counted towards the queue size. With permessage-deflate compression, a single read can decompress many megabytes of data, potentially exhausting memory.
AIOHTTP suffers from a vulnerability where decompressing payloads composed of many concatenated compressed members causes excessive CPU usage due to quadratic time complexity. This can block the event loop of servers or clients when processing specially crafted compressed request bodies or WebSocket messages. The issue affects versions >=3.27.1_1 and <3.27.1_2 and has been fixed in version 3.27.1_2.
A vulnerability in AIOHTTP's pure-Python HTTP parser causes the request buffer to grow excessively when handling pipelined requests after a declined upgrade. This leads to repeated processing of already-handled requests and excessive memory consumption. The issue affects users relying on the Python parser instead of the default C parser. A fix is available in version 3.27.1_2.