https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2020-24335.htmlhttps://patchthecve.com/cve/CVE-2020-24335.htmlWed, 17 Jun 2026 03:05:23 +0000HIGH 7.5: An issue was discovered in uIP through 1.0, as used in Contiki and Contiki-NG. Domain name parsing lacks bounds checks, allowing an attacker to corrupt memory with crafted DNS packets.https://patchthecve.com/cve/CVE-2020-24334.htmlhttps://patchthecve.com/cve/CVE-2020-24334.htmlWed, 17 Jun 2026 03:05:23 +0000HIGH 8.2: The code that processes DNS responses in uIP through 1.0, as used in Contiki and Contiki-NG, does not check whether the number of responses specified in the DNS packet header corresponds to the response data available in the DNS packet, leading to an out-of-bounds read and Denial-of-Service in resolhttps://patchthecve.com/cve/CVE-2020-17440.htmlhttps://patchthecve.com/cve/CVE-2020-17440.htmlWed, 17 Jun 2026 02:58:56 +0000HIGH 7.5: An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that parses incoming DNS packets does not validate that domain names present in the DNS responses have '\0' termination. This results in errors when calculating the offset of the pointer that jumps over domain nahttps://patchthecve.com/cve/CVE-2020-17439.htmlhttps://patchthecve.com/cve/CVE-2020-17439.htmlWed, 17 Jun 2026 02:58:56 +0000HIGH 8.3: An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that parses incoming DNS packets does not validate that the incoming DNS replies match outgoing DNS queries in newdata() in resolv.c. Also, arbitrary DNS replies are parsed if there was any outgoing DNS query withttps://patchthecve.com/cve/CVE-2020-17438.htmlhttps://patchthecve.com/cve/CVE-2020-17438.htmlWed, 17 Jun 2026 02:58:55 +0000CRITICAL 9.8: An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that reassembles fragmented packets fails to properly validate the total length of an incoming packet specified in its IP header, as well as the fragmentation offset value specified in the IP header. By crafting https://patchthecve.com/cve/CVE-2020-17437.htmlhttps://patchthecve.com/cve/CVE-2020-17437.htmlWed, 17 Jun 2026 02:58:55 +0000HIGH 8.2: An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. When the Urgent flag is set in a TCP packet, and the stack is configured to ignore the urgent data, the stack attempts to use the value of the Urgent pointer bytes to separate the Urgent data from the normal data, by calchttps://patchthecve.com/cve/CVE-2020-13987.htmlhttps://patchthecve.com/cve/CVE-2020-13987.htmlWed, 17 Jun 2026 02:54:03 +0000HIGH 7.5: An issue was discovered in Contiki through 3.0. An Out-of-Bounds Read vulnerability exists in the uIP TCP/IP Stack component when calculating the checksums for IP packets in upper_layer_chksum in net/ipv4/uip.c.