Uip Project Uip vulnerabilities

7 known vulnerabilities affecting uip_project/uip.

Total CVEs
7
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL1HIGH6

Vulnerabilities

Page 1 of 1
CVE-2020-24335HIGHCVSS 7.5≤ 1.02021-02-02
CVE-2020-24335 [HIGH] CWE-125 CVE-2020-24335: An issue was discovered in uIP through 1.0, as used in Contiki and Contiki-NG. Domain name parsing l 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.
nvd
CVE-2020-17438CRITICALCVSS 9.8v1.02020-12-11
CVE-2020-17438 [CRITICAL] CWE-787 CVE-2020-17438: An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that reassem 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 a packet with specific values of the IP header le
nvd
CVE-2020-17439HIGHCVSS 8.3v1.02020-12-11
CVE-2020-17439 [HIGH] CWE-20 CVE-2020-17439: An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that parses 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 with a transaction ID that matches the transaction ID of a
nvd
CVE-2020-24334HIGHCVSS 8.2≤ 1.02020-12-11
CVE-2020-24334 [HIGH] CWE-125 CVE-2020-24334: The code that processes DNS responses in uIP through 1.0, as used in Contiki and Contiki-NG, does no 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 resolv.c.
nvd
CVE-2020-17440HIGHCVSS 7.5v1.02020-12-11
CVE-2020-17440 [HIGH] CVE-2020-17440: An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that parses 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 name bytes in DNS response packets when a name lacks this termin
nvd
CVE-2020-13987HIGHCVSS 7.5≤ 1.02020-12-11
CVE-2020-13987 [HIGH] CWE-125 CVE-2020-13987: An issue was discovered in Contiki through 3.0. An Out-of-Bounds Read vulnerability exists in the uI 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.
nvd
CVE-2020-17437HIGHCVSS 8.2≤ 1.02020-12-11
CVE-2020-17437 [HIGH] CWE-787 CVE-2020-17437: An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. When the Urgent flag 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 calculating the offset at which the normal data should be
nvd