16 results (0.014 seconds)

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

19 Jun 2023 — VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 does not check the transport layer length in a frame before performing port filtering. VirtualSquare picoTCP (también conocido como PicoTCP-NG) a través de la versión 2.1 no comprueba la longitud de la capa de transporte en una trama antes de realizar el filtrado de puertos. • https://github.com/virtualsquare/picotcp/commit/d561990a358899178115e156871cc054a1c55ffe •

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

19 Jun 2023 — VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 does not have an MSS lower bound (e.g., it could be zero). VirtualSquare picoTCP (también conocido como PicoTCP-NG) a través de la versión 2.1 no tiene un límite inferior de "MSS" (por ejemplo, podría ser cero). • https://github.com/virtualsquare/picotcp/commit/eaf166009e44641e6570c576ba071217f100fd99 • CWE-908: Use of Uninitialized Resource •

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

19 Jun 2023 — VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 lacks certain size calculations before attempting to set a value of an mss structure member. VirtualSquare picoTCP (también conocido como PicoTCP-NG) a través de la versión 2.1 carece de ciertos cálculos de tamaño antes de intentar establecer un valor de un miembro de la estructura "mss". • https://github.com/virtualsquare/picotcp/pull/15/files • CWE-682: Incorrect Calculation •

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

19 Jun 2023 — VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 does not properly check whether header sizes would result in accessing data outside of a packet. VirtualSquare picoTCP (también conocido como PicoTCP-NG) a través de la versión 2.1 no comprueba correctamente si los tamaños de cabecera resultarían en un acceso a lo datos fuera de un paquete. • https://github.com/virtualsquare/picotcp/commit/4b9a16764f2b12b611de9c34a50b4713d10ca401 • CWE-754: Improper Check for Unusual or Exceptional Conditions •

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

19 Apr 2023 — Altran picoTCP through 1.7.0 allows memory corruption (and subsequent denial of service) because of an integer overflow in pico_ipv6_alloc when processing large ICMPv6 packets. This affects installations with Ethernet support in which a packet size greater than 65495 may occur. • https://georgyg.com/home/picotcp-denial-of-service-cve-2023-30463 • CWE-190: Integer Overflow or Wraparound •

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

11 Dec 2020 — 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 leads to an out-of-bounds read when assembling received packets into a data segment, eventually causing Denial-of-Service or an information leak. Se detectó un problema en picoTCP y picoTCP-NG versiones hasta 1.7.0. La función de procesamiento de datos de entrada TCP en el archivo pico_tcp.c no comprueba la longitud de los paqu... • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 • CWE-125: Out-of-bounds Read •

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

11 Dec 2020 — 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. Se detectó un problema en picoTCP y picoTCP-NG versiones hasta 1.7.0. El código que procesa las respuestas DNS ... • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 • CWE-125: Out-of-bounds Read •

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

11 Dec 2020 — 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 validate the compression pointer offset values with respect to the actual data present in a DNS response packet, causing out-of-bounds reads that lead to Denial-of-Service. Se detectó un problema en picoTCP y picoTCP-NG versiones hasta 1.7.0. La funcionalidad de descompresión de registros de nombres de dominio DNS en la funci... • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 • CWE-125: Out-of-bounds Read •

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

11 Dec 2020 — 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. Se detectó un problema en picoTCP versiones hasta 1.7.0. La funcionalidad de descompresión de registros de nombres de dominio DNS en la funció... • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 • CWE-787: Out-of-bounds Write •

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

11 Dec 2020 — 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. Se detectó un problema en picoTCP y picoTCP-NG versiones hasta 1.7.0. Cuando se proporciona una opción TCP no compatible con longitud cero en un paquete TCP entrante, es posible causar una Denegación de Se... • https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •