DeutschShown in its original language — a full translation is planned for a future version.
TCP/IP Stack: Mehrere Schwachstellen
view advisory published 2020-12-08
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in TCP/IP Stack ausnutzen, um beliebigen Programmcode mit Administratorrechten auszuführen, einen Denial of Service Angriff durchzuführen, vertrauliche Daten einzusehen oder Daten zu manipulieren.
01
describes (33)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-24335US | high7.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 pack… | ||||
| CVE-2020-25112US | critical9.8 | — | ||
An issue was discovered in the IPv6 stack in Contiki through 3.0. There are inconsistent checks for IPv6 header extension lengths. This leads to Denial-of-Service and potential Rem… | ||||
| CVE-2020-25111US | critical9.8 | — | ||
An issue was discovered in the IPv6 stack in Contiki through 3.0. There is an insufficient check for the IPv6 header length. This leads to Denial-of-Service and potential Remote Co… | ||||
| CVE-2020-25110US | critical9.8 | — | ||
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 query/response is not checked, and is used for internal memor… | ||||
| CVE-2020-25109US | critical9.8 | — | ||
An issue was discovered in the DNS implementation in Ethernut in Nut/OS 5.1. The number of DNS queries/responses (set in a DNS header) is not checked against the data present. This… | ||||
| CVE-2020-25108US | critical9.8 | — | ||
An issue was discovered in the DNS implementation in Ethernut in Nut/OS 5.1. The DNS response data length is not checked (it can be set to an arbitrary value from a packet). This m… | ||||
| CVE-2020-25107US | critical9.8 | — | ||
An issue was discovered in the DNS implementation in Ethernut in Nut/OS 5.1. There is no check on whether a domain name has '\0' termination. This may lead to successful Denial-of-… | ||||
| CVE-2020-24383US | critical9.1 | — | ||
An issue was discovered in FNET through 4.6.4. The code for processing resource records in mDNS queries doesn't check for proper '\0' termination of the resource record name string… | ||||
| CVE-2020-24341US | critical9.1 | — | ||
An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. The TCP input data processing function in pico_tcp.c does not validate the length of incoming TCP packets, which le… | ||||
| CVE-2020-24340US | high7.5 | — | ||
An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. The code that processes DNS responses in pico_mdns_handle_data_as_answers_generic() in pico_mdns.c does not check w… | ||||
| CVE-2020-24339US | high7.5 | — | ||
An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. The DNS domain name record decompression functionality in pico_dns_decompress_name() in pico_dns_common.c does not… | ||||
| CVE-2020-24338US | critical9.8 | — | ||
An issue was discovered in picoTCP through 1.7.0. The DNS domain name record decompression functionality in pico_dns_decompress_name() in pico_dns_common.c does not validate the co… | ||||
| CVE-2020-24337US | high7.5 | — | ||
An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. When an unsupported TCP option with zero length is provided in an incoming TCP packet, it is possible to cause a De… | ||||
| CVE-2020-24336US | critical9.8 | — | ||
An issue was discovered in Contiki through 3.0 and Contiki-NG through 4.5. The code for parsing Type A domain name answers in ip64-dns64.c doesn't verify whether the address in the… | ||||
| CVE-2020-24334US | high8.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 corre… | ||||
| CVE-2020-17470US | medium5.3OT elevated | — | ||
An issue was discovered in FNET through 4.6.4. The code that initializes the DNS client interface structure does not set sufficiently random transaction IDs (they are always set to… | ||||
| CVE-2020-17469US | high7.5 | — | ||
An issue was discovered in FNET through 4.6.4. The code for IPv6 fragment reassembly tries to access a previous fragment starting from a network incoming fragment that still doesn'… | ||||
| CVE-2020-17468US | high7.5 | — | ||
An issue was discovered in FNET through 4.6.4. The code for processing the hop-by-hop header (in the IPv6 extension headers) doesn't check for a valid length of an extension header… | ||||
| CVE-2020-17467US | critical9.1 | — | ||
An issue was discovered in FNET through 4.6.4. The code for processing the hostname from an LLMNR request doesn't check for '\0' termination. Therefore, the deduced length of the h… | ||||
| CVE-2020-17445US | high7.5 | — | ||
An issue was discovered in picoTCP 1.7.0. The code for processing the IPv6 destination options does not check for a valid length of the destination options header. This results in… | ||||
showing 20 of 33
02
references
External citations — patches, advisories, analysis.
- SUSE Security Update SUSE-SU-2021:1164-1 vom 2021-04-13external
- SUSE Security Update SUSE-SU-2021:0663-1 vom 2021-03-01external
- SUSE Security Update SUSE-SU-2022:2806-1 vom 2022-08-15external
- SUSE Security Update SUSE-SU-2022:2861-1 vom 2022-08-22external
- Unify Security Advisory Report OBSO-2101-01 vom 2021-01-08external
- Ubuntu Security Notice USN-6259-1 vom 2023-07-27external
- US ICS CERT Advisory ICSA-20-343-01 vom 2020-12-08external
- WID-SEC-W-2022-1044 - CSAF Versionself
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan