CVE-2023-35849

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not properly check whether header sizes would result in accessing data outside of a packet...

CVE-2023-35848: Incorrect Calculation

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 lacks certain size calculations before attempting to set a value of an mss structure member...

CVE-2023-35846: Undefined Security Weakness

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not check the transport layer length in a frame before performing port filtering...

CVE-2023-35847: Use of Uninitialized Resource

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not have an MSS lower bound e.g., it could be zero...

CVE-2023-35847

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not have an MSS lower bound e.g., it could be zero...

CVE-2023-35849

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not properly check whether header sizes would result in accessing data outside of a packet...

CVE-2023-35846

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not check the transport layer length in a frame before performing port filtering...

CVE-2023-35846

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not check the transport layer length in a frame before performing port filtering...

CVE-2023-35847

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not have an MSS lower bound e.g., it could be zero...

CVE-2023-35848

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 lacks certain size calculations before attempting to set a value of an mss structure member...

CVE-2023-35846

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not check the transport layer length in a frame before performing port filtering...

PT-2023-25339 · Virtualsquare · Picotcp

Name of the Vulnerable Software and Affected Versions: VirtualSquare picoTCP aka PicoTCP-NG versions 2.1 and earlier Description: The issue arises from the failure to check the transport layer length in a frame before performing port filtering. This can lead to potential security risks...

CVE-2023-35847

CVE-2023-35847 affects VirtualSquare picoTCP (aka PicoTCP-NG) up to version 2.1, where the MSS lower bound is not enforced (could be zero). The provided documents consistently describe the vulnerability as stemming from the lack of an MSS lower bound, but do not specify an affected vendor/version...

CVE-2023-35847

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 does not have an MSS lower bound e.g., it could be zero...

CVE-2023-35848

VirtualSquare picoTCP aka PicoTCP-NG through 2.1 lacks certain size calculations before attempting to set a value of an mss structure member...

PT-2023-25342 · Virtualsquare · Virtualsquare Picotcp

Name of the Vulnerable Software and Affected Versions: VirtualSquare picoTCP aka PicoTCP-NG versions 2.1 and earlier Description: The issue arises from improper checking of header sizes, which could lead to accessing data outside of a packet. Recommendations: For VirtualSquare picoTCP aka...

CVE-2023-35846

VirtualSquare PicoTCP-NG (aka PicoTCP-NG) up to version 2.1 is affected by a vulnerability in which the transport-layer length is not checked within a frame before port filtering. The issue is described across multiple sources as affecting the PicoTCP-NG stack (VirtualSquare) and is associated wi...

CVE-2023-35849

The CVE-2023-35849 entry concerns VirtualSquare picoTCP (PicoTCP-NG) up to version 2.1. The vulnerability is caused by improper checking of header sizes, which can result in accessing data outside of a packet. The available sources indicate this affects PicoTCP-NG 2.1 and earlier, with CVSS v3.1 ...

CVE-2023-35848

CVE-2023-35848 affects VirtualSquare PicoTCP-NG (aka picoTCP) up to version 2.1. The root cause is missing size calculations before setting a value in an mss structure member, which can impact packet processing. Documented impact per CVSS indicates high impact to availability with no confidential...

PT-2023-25340 · Virtualsquare · Virtualsquare Picotcp

Name of the Vulnerable Software and Affected Versions: VirtualSquare picoTCP aka PicoTCP-NG versions through 2.1 Description: The issue is related to the lack of a Maximum Segment Size MSS lower bound, which could potentially be set to zero. This affects the VirtualSquare picoTCP aka PicoTCP-NG...