Please consider checking the list of known issues before using picoTCP in production.
Vulnerabilities that can be found in picoTCP-NG v.2.1:
- None currently known.
Vulnerabilities fixed in this version:
-
Improper checks against the payload length field of IPv6 extension headers which may lead to an information leak or denial of service (CVE-2020-17441)
- Fixed in v2.1 ✔️
-
Improper checks against the length of the Hop-by-Hop extension header may result in an infinite loop which leads to a denial of service (CVE-2020-17442)
- Fixed in v2.1 ✔️
-
Improper checks against ICMPv6 headers when processing ICMPv6 echo requests may lead to a denial of service (CVE-2020-17443)
- Fixed in v2.1 ✔️
-
Improper checks against the lengths of extension header options when processing IPv6 headers may result into a denial of service (CVE-2020-17444)
- Fixed in v2.1 ✔️
-
Improper checks against options lengths when processing the IPv6 Destination Options extension header may result in a denial of service (CVE-2020-17445)
- Fixed in v2.1 ✔️
-
Improper length validation of TCP options in IPv4 may results in a denial of service (CVE-2020-24337)
- Fixed in v2.1 ✔️
-
Improper checks against the length of incoming TCP packets may enable an out-of-bound read and/or memory corruption (CVE-2020-24341)
- Fixed in v2.1 ✔️
-
Improper checks in the process of DNS response handling which may lead to memory corruption (CVE-2020-24340)
- Fixed in 2.2 ✔️
-
Improper bound checking against the parsing of domain names which may result in remote code execution (CVE-2020-24338)
- Fixed in 2.2 ✔️
-
Improper bound checking against the parsing of domain names which may result in a denial of service (CVE-2020-24339)
- Fixed in 2.2 ✔️
-
Heap buffer overflow in IP fragment reassembly due to a 16-bit length truncation (Forescout FSCT-2026-0017)
- Fixed in 2.2 ✔️
-
Address-buffer overflow in the pico_socket_accept() peer-address copy (Forescout FSCT-2026-0018)
- Fixed in 2.2 ✔️
-
Unsigned integer underflow in UDP receive leading to an out-of-bounds read (Forescout FSCT-2026-0019)
- Fixed in 2.2 ✔️
-
Out-of-bounds read in DNS client name lookup due to an unbounded name walk (Forescout FSCT-2026-0020)
- Fixed in 2.2 ✔️
-
Out-of-bounds read in IPv4 input processing due to an off-by-option-length bound check (Forescout FSCT-2026-0022)
- Fixed in 2.2 ✔️