‼ CVE-2020-24338 ‼
📖 Read
via "National Vulnerability Database".
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 compression pointer offset values with respect to the actual data present in a DNS response packet, causing out-of-bounds writes that lead to Denial-of-Service and Remote Code Execution.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17442 ‼
📖 Read
via "National Vulnerability Database".
An issue was discovered in picoTCP 1.7.0. The code for parsing the hop-by-hop IPv6 extension headers does not validate the bounds of the extension header length value, which may result in Integer Wraparound. Therefore, a crafted extension header length value may cause Denial-of-Service because it affects the loop in which the extension headers are parsed in pico_ipv6_process_hopbyhop() in pico_ipv6.c.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-24337 ‼
📖 Read
via "National Vulnerability Database".
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 Denial-of-Service by achieving an infinite loop in the code that parses TCP options, aka tcp_parse_options() in pico_tcp.c.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17469 ‼
📖 Read
via "National Vulnerability Database".
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't have a reference to the previous one (which supposedly resides in the reassembly list). When faced with an incoming fragment that belongs to a non-empty fragment list, IPv6 reassembly must check that there are no empty holes between the fragments: this leads to an uninitialized pointer dereference in _fnet_ip6_reassembly in fnet_ip6.c, and causes Denial-of-Service.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17438 ‼
📖 Read
via "National Vulnerability Database".
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 length and the fragmentation offset, attackers can write into the .bss section of the program (past the statically allocated buffer that is used for storing the fragmented data) and cause a denial of service in uip_reass() in uip.c, or possibly execute arbitrary code on some target architectures.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-25108 ‼
📖 Read
via "National Vulnerability Database".
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 may lead to successful Denial-of-Service, and possibly Remote Code Execution.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17439 ‼
📖 Read
via "National Vulnerability Database".
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 an incoming reply. Provided that the default DNS cache is quite small (only four records) and that the transaction ID has a very limited set of values that is quite easy to guess, this can lead to DNS cache poisoning.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-24383 ‼
📖 Read
via "National Vulnerability Database".
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, leading to an out-of-bounds read, and potentially causing information leak or Denial-or-Service.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-24340 ‼
📖 Read
via "National Vulnerability Database".
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 whether the number of answers/responses specified in a DNS packet header corresponds to the response data available in the packet, leading to an out-of-bounds read, invalid pointer dereference, and Denial-of-Service.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-25107 ‼
📖 Read
via "National Vulnerability Database".
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-Service, and possibly Remote Code Execution.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-25112 ‼
📖 Read
via "National Vulnerability Database".
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 Remote Code Execution via a crafted ICMPv6 echo packet.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17470 ‼
📖 Read
via "National Vulnerability Database".
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 1 in _fnet_dns_poll in fnet_dns.c). This significantly simplifies DNS cache poisoning attacks.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17441 ‼
📖 Read
via "National Vulnerability Database".
An issue was discovered in picoTCP 1.7.0. The code for processing the IPv6 headers does not validate whether the IPv6 payload length field is equal to the actual size of the payload, which leads to an Out-of-Bounds read during the ICMPv6 checksum calculation, resulting in either Denial-of-Service or Information Disclosure. This affects pico_ipv6_extension_headers and pico_checksum_adder (in pico_ipv6.c and pico_frame.c).📖 Read
via "National Vulnerability Database".
‼ CVE-2020-35175 ‼
📖 Read
via "National Vulnerability Database".
Frappe Framework 12 and 13 does not properly validate the HTTP method for the frappe.client API.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-25111 ‼
📖 Read
via "National Vulnerability Database".
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 Code Execution via a crafted ICMPv6 echo packet.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-35176 ‼
📖 Read
via "National Vulnerability Database".
In AWStats through 7.8, cgi-bin/awstats.pl?config= accepts a partial absolute pathname (omitting the initial /etc), even though it was intended to only read a file in the /etc/awstats/awstats.conf format. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000501 and CVE-2020-29600.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17437 ‼
📖 Read
via "National Vulnerability Database".
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 present in the global buffer. However, the length of this offset is not checked; therefore, for large values of the Urgent pointer bytes, the data pointer can point to memory that is way beyond the data buffer in uip_process in uip.c.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-24336 ‼
📖 Read
via "National Vulnerability Database".
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 answer's length is sane. Therefore, when copying an address of an arbitrary length, a buffer overflow can occur. This bug can be exploited whenever NAT64 is enabled.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17468 ‼
📖 Read
via "National Vulnerability Database".
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, and therefore an out-of-bounds read can occur in _fnet_ip6_ext_header_handler_options in fnet_ip6.c, leading to Denial-of-Service.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-24338 ‼
📖 Read
via "National Vulnerability Database".
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 compression pointer offset values with respect to the actual data present in a DNS response packet, causing out-of-bounds writes that lead to Denial-of-Service and Remote Code Execution.📖 Read
via "National Vulnerability Database".
‼ CVE-2020-17442 ‼
📖 Read
via "National Vulnerability Database".
An issue was discovered in picoTCP 1.7.0. The code for parsing the hop-by-hop IPv6 extension headers does not validate the bounds of the extension header length value, which may result in Integer Wraparound. Therefore, a crafted extension header length value may cause Denial-of-Service because it affects the loop in which the extension headers are parsed in pico_ipv6_process_hopbyhop() in pico_ipv6.c.📖 Read
via "National Vulnerability Database".