Afldl

The Scrypt implementation on 32-bit platforms contains an integer overflow during memory calculation due to unchecked multiplication. This allows an attacker to provide specific Scrypt parameters that wrap the allocation size, resulting in a buffer smaller than the data subsequently written. This affects systems that accept arbitrary parameters from hostile sources, such as applications decrypting attacker-supplied encrypted private keys. A triggering parameter set can cause approximately four gigabytes of data to be written past the allocated heap buffer, leading to a process crash and denial of service. While arbitrary code execution is not demonstrated, it cannot be entirely excluded.

A missing bounds check in the TLS 1.3 Certificate-message parser allows a malicious TLS 1.3 server to trigger an unsigned-integer underflow. This leads to a heap out-of-bounds read in any peer processing a remote Certificate message. The issue is reachable pre-authentication during the standard handshake process, occurring before certificate verification is completed.

The TLS 1.3 Certificate-message parser fails to verify if a message contains a byte to skip before decrementing the message length to bypass a context byte. When a zero-length Certificate message is processed, the unsigned length wraps to `0xFFFFFFFF`, rendering the subsequent bounds check ineffective and causing the parser to read beyond the session packet buffer. This issue is reachable pre-authentication and can be triggered by a four-byte handshake header without requiring cryptographic validity.

During the first DTLS ClientHello, the parser copies a device-claimed `session id` length and validates the ciphersuite-list length against the total record length rather than the remaining bytes. This allows an unauthenticated peer to trigger an Out-of-Bounds (OOB) source read of up to 255 bytes. These bytes are then echoed verbatim into the outgoing ServerHello, resulting in the disclosure of adjacent process memory over the network. A variant of this issue can also cause a crash upon receiving the first packet.

The software generates predictable cookies during the DTLS HelloVerifyRequest process. This predictability can be exploited to bypass the cookie-based mechanism intended to prevent Denial of Service (DoS) attacks, which are attempts to make a machine or network resource unavailable to its intended users.

A remote client can cause a crash of the NSD serve child process in debugging or non-release build types. This occurs when the process receives a specially crafted message containing a specific number of DNS Cookie options, such as 17 options when the UDP payload size is 512. Repeatedly crashing these processes can severely degrade performance or lead to a complete denial of DNS service.

The NTLM client lacks sanitization of a short challenge within the ` gsasl ntlm client step()` function. This flaw allows a crafted server to cause memory disclosure.