Description
In Eclipse ThreadX NetX Duo versions 6.0 through 6.5.2.202603a, the TFTP client copies the message of a received ERROR packet without bounding the copy by the end of the datagram, and the TFTP server reads one byte past a minimal ERROR packet. A malicious TFTP server can make the client copy up to 64 bytes of adjacent packet-pool memory into the error string the application retrieves, or fault on targets with memory protection.
Published: 2026-09-29
Score: 6.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Information disclosure or crash via buffer over‑read
Action: Assess
AI Analysis

Impact

The vulnerability arises in the TFTP components of Eclipse ThreadX NetX Duo when handling ERROR packets. A malformed TFTP ERROR packet causes the client to copy the packet’s message data without bounding the copy to the actual packet length, effectively a missing bounds check. The server side also reads one byte beyond the minimum size of a TFTP ERROR packet, which may trigger a fault on systems with memory protection enabled. These unchecked bounds violations can lead to the disclosure of nearby memory contents or a crash of the target device.

Affected Systems

NetX Duo from the Eclipse Foundation is affected. Versions 6.0 through 6.5.2.202603a contain the vulnerable TFTP client and server implementations. Any deployment running any of these releases and that utilizes TFTP client or server functionality should verify whether the TFTP service is required.

Risk and Exploitability

The CVSS score of 6.9 indicates medium severity. The EPSS score is below 1% and the vulnerability is not listed in the CISA KEV catalog, suggesting a low likelihood of widespread exploitation at present. Based on the description, it is inferred that an attacker with network reach to the target’s TFTP service must send a specially crafted ERROR packet. Successful exploitation could let the attacker read adjacent memory or trigger a fault, but it does not provide remote code execution or other higher‑level privileges.

Generated by OpenCVE AI on November 4, 2026 at 16:29 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a later release of Eclipse ThreadX NetX Duo that addresses the out‑of-bounds read in the TFTP client and server (CWE‑125).
  • If an upgrade cannot be performed, disable or remove the unused TFTP service to eliminate the vulnerability.
  • Restrict inbound TFTP traffic to trusted hosts using firewall rules or network segmentation to reduce exposure.

Generated by OpenCVE AI on November 4, 2026 at 16:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 04 Nov 2026 09:45:00 +0000

Type Values Removed Values Added
Description A TFTP server that answers with a short ERROR packet makes the client read up to 64 bytes past the received datagram. Each receive path checks only that the datagram is at least four bytes long (nxd_tftp_client.c:1229, 1521, 1984). When the opcode is NX_TFTP_CODE_ERROR the message string is copied with a loop whose only limits are the destination buffer and a NUL byte: ```c /* addons/tftp/nxd_tftp_client.c:1769 */ for (i = 0; (i < (sizeof(tftp_client_ptr -> nx_tftp_client_error_string) - 1)) && (*buffer_ptr); i++) ``` Nothing compares `buffer_ptr` against `nx_packet_append_ptr`. An ERROR packet that carries no terminating NUL, which a server controls completely, walks the loop off the end of the packet until it happens to meet a zero byte or fills the 64 byte destination. ``` ERROR: AddressSanitizer: heap-buffer-overflow READ of size 1 at 0x60d0000000c8 thread T4 #0 _nxd_tftp_client_file_read addons/tftp/nxd_tftp_client.c:1769 0x60d0000000c8 is 0 bytes to the right of 136-byte region ``` The open path has the same loop at :1327 and reports the same way. What is read lands in `nx_tftp_client_error_string`, which the application is expected to display or log, so adjacent packet pool memory ends up in whatever the device does with the error text. Add `(buffer_ptr < packet_ptr -> nx_packet_append_ptr)` to the loop condition in all three paths. In Eclipse ThreadX NetX Duo versions 6.0 through 6.5.2.202603a, the TFTP client copies the message of a received ERROR packet without bounding the copy by the end of the datagram, and the TFTP server reads one byte past a minimal ERROR packet. A malicious TFTP server can make the client copy up to 64 bytes of adjacent packet-pool memory into the error string the application retrieves, or fault on targets with memory protection.
Title TFTP Client Buffer Overflow via Malformed ERROR Packet TFTP client and server copy the ERROR packet message without bounding the read against the packet

Wed, 30 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Eclipse
Eclipse netx Duo
Vendors & Products Eclipse
Eclipse netx Duo

Tue, 29 Sep 2026 22:15:00 +0000

Type Values Removed Values Added
Title TFTP Client Buffer Overflow via Malformed ERROR Packet

Tue, 29 Sep 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Tue, 29 Sep 2026 18:00:00 +0000

Type Values Removed Values Added
Description A TFTP server that answers with a short ERROR packet makes the client read up to 64 bytes past the received datagram. Each receive path checks only that the datagram is at least four bytes long (nxd_tftp_client.c:1229, 1521, 1984). When the opcode is NX_TFTP_CODE_ERROR the message string is copied with a loop whose only limits are the destination buffer and a NUL byte: ```c /* addons/tftp/nxd_tftp_client.c:1769 */ for (i = 0; (i < (sizeof(tftp_client_ptr -> nx_tftp_client_error_string) - 1)) && (*buffer_ptr); i++) ``` Nothing compares `buffer_ptr` against `nx_packet_append_ptr`. An ERROR packet that carries no terminating NUL, which a server controls completely, walks the loop off the end of the packet until it happens to meet a zero byte or fills the 64 byte destination. ``` ERROR: AddressSanitizer: heap-buffer-overflow READ of size 1 at 0x60d0000000c8 thread T4 #0 _nxd_tftp_client_file_read addons/tftp/nxd_tftp_client.c:1769 0x60d0000000c8 is 0 bytes to the right of 136-byte region ``` The open path has the same loop at :1327 and reports the same way. What is read lands in `nx_tftp_client_error_string`, which the application is expected to display or log, so adjacent packet pool memory ends up in whatever the device does with the error text. Add `(buffer_ptr < packet_ptr -> nx_packet_append_ptr)` to the loop condition in all three paths.
Weaknesses CWE-125
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N'}

Subscriptions

Eclipse Netx Duo
cve-icon MITRE

Status: PUBLISHED

Assigner: eclipse

Published:

Updated: 2026-11-04T09:45:51.393Z

Reserved: 2026-09-29T16:15:17.020Z

Link: CVE-2026-102721

cve-icon Vulnrichment

Updated: 2026-09-29T18:35:40.497Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-29T18:17:11.540

Modified: 2026-11-04T10:17:23.870

Link: CVE-2026-102721

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-04T16:30:13Z

Weaknesses