Apache ActiveMQ contains an input validation vulnerability in the LDAPAuthorizationMapPlugin that allows an authenticated attacker to bypass authorization by injecting LDAP DN special characters into destination names. This manipulation affects the LDAP search base used for access control list lookups. The issue affects versions 5.19.0 through 5.19.11 and 6.3.0 through 6.3.2. Fixed versions are 5.19.12 and 6.3.3 or later.
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 when messages are processed faster than the application consumes them. The issue arises because empty messages are not counted towards the queue size and compressed frames can decompress into large amounts of data. A patch is available to address this issue.
AIOHTTP suffers from a vulnerability where decompressing payloads with many concatenated compressed members causes excessive CPU usage due to quadratic time complexity. This can block the event loop of a server or client when processing specially crafted compressed request bodies or WebSocket messages. The issue affects versions 1.2.1 and later. A patch is available to address this problem.
AIOHTTP versions 1.2.1 and later have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without any size limit or flow control until the upgrade handler completes. This can lead to unbounded memory consumption if an attacker streams large amounts of data behind the upgrade request to a handler that does not promptly accept or reject the upgrade.
A vulnerability in AIOHTTP's WebSocket implementation allows bypassing the max_msg_size limit due to an integer overflow in the C extension's 64-bit arithmetic. This flaw enables an attacker to send an oversized WebSocket message after a small non-final fragment, causing unbounded memory consumption. The issue affects versions 1.2.1 and later. A patch is available to fix this integer overflow. As a workaround, users can disable the C extension by setting AIOHTTP_NO_EXTENSIONS=1 to use the unaffected Python reader.
AIOHTTP's Request.post() method had no limit on the number of URL-encoded form fields, causing insertion of many repeated keys into a MultiDict to take quadratic time on the event loop. This flaw allows an attacker to block the event loop by sending a form POST within the default client_max_size to any handler using Request.post(). A patch is available to address this issue.
AIOHTTP's client CookieJar component improperly handled Set-Cookie headers by creating additional cookies from unrecognized name=value attributes and lacked limits on the number of cookies stored or sent. This flaw allows a malicious server to cause a client to store an excessive number of cookies, leading to large Cookie headers and excessive memory and CPU usage on the client side, especially during redirects.
The vulnerability in Application.add_domain() involves inefficient wildcard matching of host masks containing two or more asterisks (*). This causes polynomial-time processing on the event loop when matching long Host headers that do not fit the mask, potentially stalling the server. The issue affects versions 1.2.1 and later. The recommended workaround is to limit domain masks to at most one wildcard. A patch addressing this inefficiency has been published.
A vulnerability in AIOHTTP's pure-Python HTTP parser causes the request buffer to grow uncontrollably when handling declined upgrade requests, leading to excessive memory use and repeated processing of pipelined requests. This affects users relying on the Python parser instead of the default C parser. A patch is available to address this issue.
A vulnerability in aiohttp's multipart handling allows bypassing the client_max_size limit when processing base64-encoded multipart parts. This can lead to excessive memory consumption or event loop blocking due to unbounded reading of the request body.
The RSS widget of the dashboard allows backend users to configure the URL of the RSS feed in the widget settings. The URL was fetched by the server without restricting the target host. Backend users with access to the dashboard could therefore make the server send HTTP requests to arbitrary hosts, including internal network services and cloud metadata endpoints, which are not reachable from the outside.