Threats Tagged 'cwe-401'

A memory leak vulnerability exists in honojs node-server versions before 2.0.10. When a WebSocket upgrade request with a missing or malformed Sec-WebSocket-Key header is sent to an upgradeWebSocket route, the request's IncomingMessage is retained indefinitely, causing unbounded memory growth. This can lead to denial of service by exhausting server memory. The issue is fixed in version 2.0.10.

Eclipse Milo versions 0.6.0 through 1.1.4 contain a vulnerability in the UASC server transport handlers where partial message chunks are not released upon channel disconnection. This allows a remote unauthenticated client to exhaust pooled direct memory by repeatedly sending incomplete chunks and disconnecting, potentially causing the server to terminate.

CVE-2026-67430 is a medium severity vulnerability in the MCP Ruby SDK prior to version 0.23.0. The issue involves the MCP::Server::Transports::StreamableHTTPTransport component not expiring sessions by default, causing unbounded retention of ServerSession objects. This can lead to memory exhaustion in the process due to repeated initialize requests. The vulnerability is fixed in version 0.23.0.

Apache Traffic Server versions 8.0.0 through 8.1.9, 9.0.0 through 9.2.14, and 10.0.0 through 10.1.3 contain a memory leak vulnerability when handling HostDB SRV records. This issue is identified as CWE-401, indicating missing release of memory after its effective lifetime. The vulnerability has a high severity with a CVSS score of 7.5 and impacts availability due to memory exhaustion. Upgrading to versions 9.2.15 or 10.1.4 addresses this issue.

The QUIC transport parameters extension handler in s2n-tls incorrectly uses s2n_alloc instead of s2n_realloc to store the peer's transport parameters. When a TLS 1.3 connection goes through a HelloRetryRequest, the handler is called twice on the same connection. On the second call, s2n_alloc zeroes the existing pointer before allocating new memory, causing the first allocation to be leaked. This can occur during normal QUIC traffic when a client offers a key share group the server does not prefer. An unauthenticated user can amplify the issue by deliberately forcing HelloRetryRequests, causing up to approximately 64 KB of unreachable memory per handshake. Over time, this can lead to increased memory consumption on long-running server processes. The unreachable memory is only reclaimed when the process is restarted. Only server-side QUIC-enabled deployments are affected. Non-QUIC TLS connections are not affected. We recommend you upgrade s2n-tls to version v1.7.6

CImg Library versions prior to 4.0.0 contain a memory leak vulnerability in the _load_analyze() function when processing Analyze/NIfTI files. The vulnerability arises because the header_size field is read without bounds checking and used to allocate memory, which is not freed if a file read error occurs. This can lead to large memory allocations being leaked on error paths, causing denial of service due to resource exhaustion. The issue affects files with extensions .hdr, .img, or .nii. Version 4.0.0 addresses this vulnerability.