Skip to content
OpenAdvisories

Summary

Successful exploitation of these vulnerabilities could allow attackers to corrupt memory, put devices into infinite loops, access unauthorized data, and/or poison DNS cache.

Vulnerabilities 33

  • Unscored —

    An issue was discovered in Contiki through 3.0. An infinite loop exists in the uIP TCP/IP stack component when processi…

  • Unscored —

    An issue was discovered in Contiki through 3.0. A memory corruption vulnerability exists in the uIP TCP/IP stack compon…

  • Unscored —

    An issue was discovered in Contiki through 3.0. An infinite loop exists in the uIP TCP/IP stack component when handling…

  • Unscored —

    An issue was discovered in Contiki through 3.0. An Out-of-Bounds Read vulnerability exists in the uIP TCP/IP Stack comp…

  • Unscored —

    An issue was discovered in Contiki through 3.0. An Integer Overflow exists in the uIP TCP/IP Stack component when parsi…

  • Unscored —

    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 pac…

  • Unscored —
    CVE-2020-17438 EPSS 19%

    An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that reassembles fragmented pac…

  • Unscored —

    An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that parses incoming DNS packet…

  • Unscored —

    An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that parses incoming DNS packet…

  • Unscored —

    An issue was discovered in picoTCP 1.7.0. The code for processing the IPv6 headers does not validate whether the IPv6 p…

  • Unscored —

    An issue was discovered in picoTCP 1.7.0. The code for parsing the hop-by-hop IPv6 extension headers does not validate …

  • Unscored —

    An issue was discovered in picoTCP 1.7.0. The code for creating an ICMPv6 echo replies doesn't check whether the ICMPv6…

  • Unscored —

    An issue was discovered in picoTCP 1.7.0. The routine for processing the next header field (and deducing whether the IP…

  • Unscored —

    An issue was discovered in picoTCP 1.7.0. The code for processing the IPv6 destination options does not check for a val…

  • Unscored —

    An issue was discovered in FNET through 4.6.4. The code for processing the hostname from an LLMNR request doesn't check…

  • Unscored —

    An issue was discovered in FNET through 4.6.4. The code for processing the hop-by-hop header (in the IPv6 extension hea…

  • Unscored —

    An issue was discovered in FNET through 4.6.4. The code for IPv6 fragment reassembly tries to access a previous fragmen…

  • Unscored —

    An issue was discovered in FNET through 4.6.4. The code that initializes the DNS client interface structure does not se…

  • Unscored —

    The code that processes DNS responses in uIP through 1.0, as used in Contiki and Contiki-NG, does not check whether the…

  • Unscored —

    An issue was discovered in uIP through 1.0, as used in Contiki and Contiki-NG. Domain name parsing lacks bounds checks,…

  • Unscored —
    CVE-2020-24336 EPSS 59%

    An issue was discovered in Contiki through 3.0 and Contiki-NG through 4.5. The code for parsing Type A domain name answ…

  • Unscored —

    An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. When an unsupported TCP option with zero length is pro…

  • Unscored —
    CVE-2020-24338 EPSS 37%

    An issue was discovered in picoTCP through 1.7.0. The DNS domain name record decompression functionality in pico_dns_de…

  • Unscored —

    An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. The DNS domain name record decompression functionality…

  • Unscored —

    An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. The code that processes DNS responses in pico_mdns_han…

  • Unscored —

    An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. The TCP input data processing function in pico_tcp.c d…

  • Unscored —

    An issue was discovered in FNET through 4.6.4. The code for processing resource records in mDNS queries doesn't check f…

  • Unscored —
    CVE-2020-25107 EPSS 54%

    An issue was discovered in the DNS implementation in Ethernut in Nut/OS 5.1. There is no check on whether a domain name…

  • Unscored —
    CVE-2020-25108 EPSS 54%

    An issue was discovered in the DNS implementation in Ethernut in Nut/OS 5.1. The DNS response data length is not checke…

  • Unscored —
    CVE-2020-25109 EPSS 54%

    An issue was discovered in the DNS implementation in Ethernut in Nut/OS 5.1. The number of DNS queries/responses (set i…

  • Unscored —
    CVE-2020-25110 EPSS 54%

    An issue was discovered in the DNS implementation in Ethernut in Nut/OS 5.1. The length byte of a domain name in a DNS …

  • Unscored —
    CVE-2020-25111 EPSS 21%

    An issue was discovered in the IPv6 stack in Contiki through 3.0. There is an insufficient check for the IPv6 header le…

  • Unscored —
    CVE-2020-25112 EPSS 28%

    An issue was discovered in the IPv6 stack in Contiki through 3.0. There are inconsistent checks for IPv6 header extensi…

Revision history

  1. #1

    ICSA-20-343-01 Multiple Embedded TCP-IP Stacks

References