18 results (0.009 seconds)

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

05 Sep 2021 — In Contiki 3.0, Telnet option negotiation is mishandled. During negotiation between a server and a client, the server may fail to give the WILL/WONT or DO/DONT response for DO and WILL commands because of improper handling of exception condition, which leads to property violations and denial of service. Specifically, a server sometimes sends no response, because a fixed buffer space is available for all responses and that space may have been exhausted. En Contiki versión 3.0, la negociación de opciones de T... • https://github.com/contiki-os/contiki/issues/2686 • CWE-754: Improper Check for Unusual or Exceptional Conditions •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

10 Aug 2021 — In Contiki 3.0, a buffer overflow in the Telnet service allows remote attackers to cause a denial of service because the ls command is mishandled when a directory has many files with long names. En Contiki versión 3.0, un desbordamiento de búfer en el servicio Telnet permite a atacantes remotos causar una denegación de servicio porque el comando ls es manejado inapropiadamente cuando un directorio presenta muchos archivos con nombres largos • https://github.com/contiki-os/contiki/issues/2687 • CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

10 Aug 2021 — In Contiki 3.0, a Telnet server that silently quits (before disconnection with clients) leads to connected clients entering an infinite loop and waiting forever, which may cause excessive CPU consumption. En Contiki versión 3.0, un servidor Telnet que se cierra silenciosamente (antes de la desconexión con los clientes) conlleva a que clientes conectados entren en un bucle infinito y esperen eternamente, lo que puede causar un consumo excesivo de la CPU • https://github.com/contiki-os/contiki/issues/2688 • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1

09 Aug 2021 — In Contiki 3.0, potential nonterminating acknowledgment loops exist in the Telnet service. When the negotiated options are already disabled, servers still respond to DONT and WONT requests with WONT or DONT commands, which may lead to infinite acknowledgment loops, denial of service, and excessive CPU consumption. En Contiki versión 3.0, se presentan posibles bucles de acuse de recibo no terminados en el servicio Telnet. Cuando las opciones negociadas están deshabilitadas, los servidores siguen respondiendo... • https://github.com/contiki-os/contiki/issues/2685 • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

24 Mar 2021 — An issue was discovered in Contiki through 3.0. When sending an ICMPv6 error message because of invalid extension header options in an incoming IPv6 packet, there is an attempt to remove the RPL extension headers. Because the packet length and the extension header length are unchecked (with respect to the available data) at this stage, and these variables are susceptible to integer underflow, it is possible to construct an invalid extension header that will cause memory corruption issues and lead to a Denia... • https://github.com/contiki-os/contiki/releases • CWE-191: Integer Underflow (Wrap or Wraparound) •

CVSS: 9.8EPSS: 1%CPEs: 2EXPL: 0

11 Dec 2020 — 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. Se detectó un problema en Contiki versiones hasta 3.0 y Contiki-NG versiones hasta 4.5. • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 • CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') •

CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0

11 Dec 2020 — 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 termination, and eventually leads to dereferencing the pointer at an invalid/arbitrary address, within newdata() and parse_name() in resolv.c. Se detectó un... • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 •

CVSS: 8.3EPSS: 0%CPEs: 2EXPL: 0

11 Dec 2020 — 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... • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 • CWE-20: Improper Input Validation •

CVSS: 9.8EPSS: 0%CPEs: 2EXPL: 0

11 Dec 2020 — 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 frag... • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 • CWE-787: Out-of-bounds Write •

CVSS: 8.2EPSS: 0%CPEs: 21EXPL: 0

11 Dec 2020 — 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... • https://cert-portal.siemens.com/productcert/pdf/ssa-541018.pdf • CWE-787: Out-of-bounds Write •