Ampaschal

**Name of the Vulnerable Software and Affected Versions** Zephyr (affected versions not specified) **Description** A bitwise shift issue in the PTP subsystem allows a remote attacker to cause undefined behavior and potential system crashes. By sending a crafted 'PTP MSG MANAGEMENT' message, an attacker can set an unvalidated negative `log announce interval` value in the port's data set. When a 'PTP MSG ANNOUNCE' message is subsequently processed, the `port timer set timeout random()` function computes a timeout using the operation `NSEC PER SEC >> -log seconds`. If the provided value is sufficiently negative, the shift amount exceeds the 64-bit integer width, triggering undefined behavior in C. This may result in a system crash via a compiler-generated illegal instruction trap on certain architectures, or produce an erroneous zero timeout leading to resource starvation loops or other logical errors. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** RIOT versions 2026.01 and earlier **Description** RIOT is an open-source microcontroller operating system designed for Internet of Things (IoT) and embedded devices. A flaw exists in the default handler for the well known core resource, `coap well known core default handler`. This handler writes user-provided data into a fixed-size buffer without sufficient validation, potentially leading to a buffer overflow. This can allow an attacker to corrupt adjacent stack locations, including the return address, resulting in denial of service or arbitrary code execution. The vulnerable operation involves writing option data and other data into the buffer. **Recommendations** Versions prior to 2026.01 should be updated.

**Name of the Vulnerable Software and Affected Versions** The product name cannot be determined. **Description** A lack of input validation allows for out of bounds reads caused by malicious or malformed packets. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** The product name cannot be determined. **Description** A malicious or malformed DNS packet without a payload can cause an out-of-bounds read, resulting in a crash (denial of service) or an incorrect computation. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** The product name cannot be determined. **Description** The issue is related to the function `dns copy qname` in `dns pack.c`, which performs a `memcpy` operation with an untrusted field. It does not check if the source buffer is large enough to contain the copied data. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** FreeRTOS-Plus-TCP versions 4.0.0 through 4.1.0 **Description** The issue is related to a buffer over-read in the DNS Response Parser of the FreeRTOS-Plus-TCP stack when parsing domain names in a DNS response. A carefully crafted DNS response with a domain name length value greater than the actual domain name length could cause the parser to read beyond the DNS response buffer. This affects applications using the DNS functionality of the FreeRTOS-Plus-TCP stack. Applications not using DNS functionality are not affected. **Recommendations** For FreeRTOS-Plus-TCP versions 4.0.0 through 4.1.0, update to version 4.1.1 to resolve the issue. As a temporary workaround, consider disabling the DNS functionality until a patch is available. Restrict access to the DNS Response Parser to minimize the risk of exploitation. Avoid using the DNS functionality in the affected API endpoints until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Contiki-NG versions 4.9 and prior **Description** Contiki-NG is an operating system for internet-of-things devices. The issue arises during IPHC header decompression when processing IPv6 header fields. Specifically, the system fails to check if the received packet buffer contains enough data before decompressing the IPv6 address, allowing up to 16 bytes to be read out of bounds. This is due to the statement `memcpy(&ipaddr->u8[16 - postcount], iphc ptr, postcount);`, where the value of `postcount` can be controlled by an attacker based on the address compression used in the received packet. As a result, an attacker can inject a packet that causes an out-of-bound read. **Recommendations** For Contiki-NG versions 4.9 and prior, as a temporary workaround, apply the changes in Contiki-NG pull request #2509 to patch the system. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Contiki-NG versions prior to 4.9 **Description** The issue arises when the Contiki-NG OS processes ICMP DAO packets in the `dao input storing` function without verifying that the packet buffer is sufficiently large, leading to potential out-of-bounds reads of up to 16 bytes. An attacker can exploit this by truncating an ICMP packet, causing the system to access data beyond the buffer's bounds. **Recommendations** For Contiki-NG versions prior to 4.9, apply the changes in Contiki-NG pull request #2435 to patch the system. For version 4.9 and later, no action is required as the issue is expected to be resolved in this release.