18 results (0.004 seconds)

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

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 Telnet es manejada inapropiadamente. Durante la negociación entre un servidor y un cliente, el servidor puede fallar en dar la respuesta WILL/WONT o DO/DONT para los comandos DO y WILL debido a un manejo inapropiado de la condición de excepción, que conlleva a violaciones de las propiedades y a una denegación del servicio. • https://github.com/contiki-os/contiki/issues/2686 • CWE-754: Improper Check for Unusual or Exceptional Conditions •

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

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

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

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 a las peticiones DONT y WONT con comandos WONT o DONT, lo que puede conllevar a bucles de reconocimiento infinitos, denegación de servicio y consumo excesivo de CPU • https://github.com/contiki-os/contiki/issues/2685 • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

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

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 Denial-of-Service condition. This is related to rpl-ext-header.c. Se detectó un problema en Contiki versiones hasta 3.0. • https://github.com/contiki-os/contiki/releases https://www.kb.cert.org/vuls/id/815128 • CWE-191: Integer Underflow (Wrap or Wraparound) •