Base de CVEs

In USBX before 6.4.3, the USB support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _ux_host_class_audio_streaming_sampling_get() when parsing a descriptor of an USB streaming device.

In NetX Duo before 6.4.4, the networking support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _nx_ipv4_packet_receive() when handling unicast DHCP messages that could cause corruption of 4 bytes of memory.

In Eclipse Foundation NetX Duo before 6.4.4, the networking support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _nx_ipv4_option_process() when processing an IPv4 packet with the timestamp option.

Existe uma vulnerabilidade na lógica de conversão de BigInt para string do motor QuickJS (js_bigint_to_string1), causada por um cálculo incorreto do número de dígitos necessários, o que leva à leitura de memória além da estrutura BigInt alocada. * A função determina o número de caracteres (n_digits) necessários para a representação em string pelo cálculo: n_digits = (n_bits + log2_radix - 1) / log2_radix. Essa fórmula apresenta erro de uma unidade (off-by-one) em certos casos extremos ao calcular os limbs de memória necessários. Por exemplo, um BigInt de 127 bits usando radix 32 (onde log2_radix = 5) é calculado como precisando de n_digits = 26. * O número máximo de bits efetivamente armazenados é n_bits = 127, o que exige apenas dois limbs de 64 bits (JS_LIMB_BITS = 64). * O laço de conversão itera n_digits = 26 vezes, tentando ler 5 bits em cada iteração, totalizando 26 x 5 = 130 bits. * Nas últimas iterações do laço, o código tenta ler dados que se estendem por dois limbs: c = (r->tab[pos] >> shift) | (r->tab[pos + 1] << (JS_LIMB_BITS - shift)); * Como o BigInt foi alocado com apenas dois limbs, a leitura de r->tab[pos + 1] torna-se uma leitura fora dos limites (Out-of-Bounds Read) quando pos aponta para o último limb válido (por exemplo, pos = 1). Essa vulnerabilidade permite que um atacante faça o motor ler e processar dados da memória imediatamente posterior ao buffer do BigInt. Isso pode levar à divulgação de informações sensíveis armazenadas no heap adjacente ao objeto BigInt.

A vulnerability stemming from floating-point arithmetic precision errors exists in the QuickJS engine's implementation of TypedArray.prototype.indexOf() when a negative fromIndex argument is supplied. * The fromIndex argument (read as a double variable, $d$) is used to calculate the starting position for the search. * If d is negative, the index is calculated relative to the end of the array by adding the array's length (len) to d: $$d_{new} = d + \text{len}$$ * Due to the inherent limitations of floating-point arithmetic, if the negative value $d$ is extremely small (e.g., $-1 \times 10^{-20}$), the addition $d + \text{len}$ can result in a loss of precision, yielding an outcome that is exactly equal to $\text{len}$. * The result is then converted to an integer index $k$: $k = \text{len}$. * The search function proceeds to read array elements starting from index $k$. Since valid indices are $0$ to $\text{len}-1$, starting the read at index $\text{len}$ is one element past the end of the array. This allows an attacker to cause an Out-of-Bounds Read of one element immediately following the buffer. While the scope of this read is small (one element), it can potentially lead to Information Disclosure of adjacent memory contents, depending on the execution environment.

A weakness has been identified in GNU Binutils 2.45. The affected element is the function vfinfo of the file ldmisc.c. Executing a manipulation can lead to out-of-bounds read. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. This patch is called 16357. It is best practice to apply a patch to resolve this issue.

In NetX Duo before 6.4.4, the networking support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _nx_ip_packet_receive() function when received an Ethernet with type set as IP but no IP data.

In NetX Duo before 6.4.4, the networking support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _nx_ipv4_packet_receive() function when received an Ethernet frame with less than 4 bytes of IP packet.

In NetX Duo version before 6.4.4, the component of Eclipse Foundation ThreadX, there was a potential out of bound read in _nx_secure_tls_process_clienthello() because of a missing validation of PSK length provided in the user message.

Animate versions 23.0.13, 24.0.10 and earlier are affected by an out-of-bounds read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to disclose sensitive information stored in memory. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Out-of-bounds read in Windows Routing and Remote Access Service (RRAS) allows an unauthorized attacker to disclose information over a network.

Out-of-bounds read in Windows Routing and Remote Access Service (RRAS) allows an unauthorized attacker to disclose information over a network.