Eclipse ThreadX NetX Duo vulnerabilities
18 known vulnerabilities in Eclipse ThreadX NetX Duo from Eclipse Foundation. 18 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 8.7 High severity
Eclipse ThreadX NetX Duo: Unchecked Return Value
In Eclipse ThreadX NetX Duo versions 6.4.5.202504 through 6.5.2.202603a, built with IPv6 path MTU discovery, the ICMPv6 Packet Too Big handler uses the destination-table entry it adds without checking that the add succeeded. A sender on the network can fill th
- 8.8 High severity
Eclipse ThreadX - NetX Duo: Use of Uninitialized Variable
The Web add-on's HTTP server dereferences and releases an uninitialized pointer when it detects a `Content-Length` underflow while processing a `PUT` request. The condition is reachable by an unauthenticated remote client with a single malformed request.
- 9.3 Critical severity
Eclipse ThreadX - NetX Duo: Out-of-bounds Write
The X.509 parser in NetX Secure accepts an RSA public key of any size, but every signature-verification path decrypts into fixed-size buffers dimensioned for the `NX_CRYPTO_MAX_RSA_MODULUS_SIZE` default of 4096 bits. A certificate carrying a larger modulus dri
- 8.7 High severity
Eclipse ThreadX - NetX Duo: Out-of-bounds Read
The TLS 1.3 Certificate-message parser in NetX Secure decrements the message length to skip a context byte without first establishing that the message has a byte to skip. A zero-length Certificate message therefore wraps the unsigned length to `0xFFFFFFFF`, wh
- 8.7 High severity
Eclipse ThreadX - NetX Duo: Out-of-bounds Read
A missing bounds check in the TLS 1.3 Certificate-message parser of NetX Secure lets a malicious TLS 1.3 server trigger an unsigned-integer underflow and a subsequent heap out-of-bounds read in any peer that processes a remote Certificate message. It is reacha
- 8.7 High severity
Eclipse ThreadX NetX Duo: Out-of-bounds Read
In Eclipse ThreadX NetX Duo versions up to and including 6.5.2.202603, the NetX Secure X.509 parser accepts a certificate whose signature is an empty BIT STRING and records a signature length of 0xFFFFFFFF. A remote peer can present such a certificate during t
- 9.3 Critical severity
Eclipse ThreadX - NetX Duo: Out-of-bounds Write
Out-of-bounds write via the TLS 1.3 handshake message cache in NetX Duo in Eclipse ThreadX NetX Duo 6.5.1.202602 allows a handshake message larger than the cache writes past it and on into the rest of the session control block, which holds pointers. A maliciou
- 7.1 High severity
Eclipse ThreadX NetX Duo: Out-of-bounds Read
In Eclipse ThreadX NetX Duo versions 6.0 through 6.5.2.202603a, the PPP IPCP code parses a peer's Configure-Nak without validating each option's length. A malicious PPP peer can stall the PPP thread indefinitely with a zero-length option, taking the link down,
- 7.1 High severity
Eclipse ThreadX NetX Duo: Out-of-bounds Read
In Eclipse ThreadX NetX Duo versions 6.4.0 through 6.5.2.202603a, built with VLAN and SRP support, the MSRP parser uses the attribute list length from the received frame without comparing it with the packet length. An unauthenticated station on the same Layer
- 7.1 High severity
Eclipse ThreadX NetX Duo: NULL Pointer Dereference
In Eclipse ThreadX NetX Duo versions 6.4.0 through 6.5.2.202603a, built with VLAN and SRP support, evicting the last attribute in an MRP participant's list writes through a null successor pointer. An unauthenticated station on the same Layer 2 segment can faul
- 7.1 High severity
Eclipse ThreadX NetX Duo: NULL Pointer Dereference
In Eclipse ThreadX NetX Duo versions 6.4.0 through 6.5.2.202603a, built with VLAN and SRP support, the MSRP attribute lookup writes through the null pointer returned by its allocator when the ten-entry attribute table is full. An unauthenticated station on the
- 8.7 High severity
Eclipse ThreadX NetX Duo: Out-of-bounds Read
In Eclipse ThreadX NetX Duo versions up to and including 6.5.2.202603, the SNMP agent's OID parser uses a multi-byte BER length from the request without checking it against the bytes present, and reads past the end of the packet buffer. A remote, unauthenticat
- 8.7 High severity
Eclipse ThreadX NetX Duo: Missing Release of Memory after Effective Lifetime
In Eclipse ThreadX NetX Duo versions up to and including 6.5.2.202603, the RTSP server returns a raw parser error for a malformed Session header and never releases the response packet it allocated. An unauthenticated client can drain the server's packet pool w
- 7.1 High severity
Eclipse ThreadX NetX Duo: Incorrect Comparison
In Eclipse ThreadX NetX Duo versions up to and including 6.5.2.202603, the mDNS add-on's string cache accepts a shorter name as a match for a longer stored one. A host on the local link can send two mDNS records that make a device performing continuous service
- 7.1 High severity
Eclipse ThreadX NetX Duo: Out-of-bounds Read
In Eclipse ThreadX NetX Duo versions up to and including 6.5.2.202603, built with IPv6, the ICMPv6 option validator accepts an option area that ends in a one- or two-byte residue, and the Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and
- 8.3 High severity
Eclipse ThreadX NetX Duo: Out-of-bounds Read
In Eclipse ThreadX NetX Duo versions up to and including 6.5.2.202603, built with packet chaining, the TFTP server does not bound the length of a received DATA datagram. An unauthenticated peer can upload an oversized datagram that writes memory beyond the rec
- 7.5 High severity
Eclipse ThreadX - NetX Duo: Incomplete Cleanup
The security fix for CVE-2025-0728 in eclipse-threadx NetX Duo refactors error handling in the HTTP server PUT process to use a shared cleanup label, but this unified cleanup path unconditionally calls fx_file_close() even when the file was never successfully
- 7.5 High severity
Eclipse ThreadX - NetX Duo: Uncontrolled Resource Consumption
A denial-of-service vulnerability exists in the NetX IPv6 component functionality of Eclipse ThreadX NetX Duo. A specially crafted network packet of "Packet Too Big" with more than 15 different source address can lead to denial of service. An attacker can send