CVE-2026-102758: CWE-126 Buffer Over-read in Eclipse Foundation NetX Duo
The `_nx_secure_x509_asn1_tlv_block_parse()` function parses ASN.1 TLV (tag-length-value) blocks out of DER-encoded data. It is the primitive underneath all X.509 certificate parsing in NetX Secure, and therefore runs on certificates supplied by a remote peer during the TLS handshake. The function reads the one-byte ASN.1 tag from the caller's buffer *before* checking that the buffer holds at least one byte. When a caller passes a remaining length of zero, the guard correctly returns `NX_SECURE_X509_ASN1_LENGTH_TOO_LONG`, but the read has already happened one byte past the end of the buffer. code: nx_secure/src/nx_secure_x509_asn1_tlv_block_parse.c ``` UINT _nx_secure_x509_asn1_tlv_block_parse(const UCHAR *buffer, ULONG *buffer_length, USHORT *tlv_type, USHORT *tlv_tag_class, ULONG *tlv_length, const UCHAR **tlv_data, ULONG *header_length) { UINT current_index; USHORT current_tag; ULONG length; ULONG length_bytes; current_index = 0; current_tag = buffer[current_index]; /* <-- read before the bounds check */ if (*buffer_length < 1) { return(NX_SECURE_X509_ASN1_LENGTH_TOO_LONG); } ``` The remainder of the function is correctly ordered. The multi-byte length path is guarded by `length_bytes > 4 || length_bytes > *buffer_length` before its read loop, the decoded value is checked against `length > *buffer_length`, and the second single-byte length read follows its own `*buffer_length < 1` guard. The tag read is the only load placed ahead of its check.
AI Analysis
Technical Summary
The _nx_secure_x509_asn1_tlv_block_parse() function in NetX Duo parses ASN.1 TLV blocks from DER-encoded data used in X.509 certificate parsing. It reads the ASN.1 tag byte from the buffer before checking if the buffer length is at least one byte, leading to a buffer over-read (CWE-126) when the buffer length is zero. Subsequent length checks in the function are correctly implemented, but the initial tag read occurs out-of-bounds. This vulnerability affects versions from 0 up to and including 6.5.1.202602 of NetX Duo.
Potential Impact
This buffer over-read vulnerability could cause the function to read memory beyond the provided buffer, potentially leading to application crashes or information disclosure depending on how the parsed data is used. The vulnerability occurs during TLS handshake certificate parsing, which may impact the security or stability of TLS connections using NetX Duo. No known exploits are reported in the wild at this time.
Mitigation Recommendations
No vendor advisory or patch information is provided for this vulnerability. Patch status is not yet confirmed — check the Eclipse Foundation or NetX Duo vendor advisories for current remediation guidance. Until a fix is available, users should consider mitigating exposure by validating input buffers before passing them to the vulnerable function or applying any recommended vendor mitigations once published.
CVE-2026-102758: CWE-126 Buffer Over-read in Eclipse Foundation NetX Duo
Description
The `_nx_secure_x509_asn1_tlv_block_parse()` function parses ASN.1 TLV (tag-length-value) blocks out of DER-encoded data. It is the primitive underneath all X.509 certificate parsing in NetX Secure, and therefore runs on certificates supplied by a remote peer during the TLS handshake. The function reads the one-byte ASN.1 tag from the caller's buffer *before* checking that the buffer holds at least one byte. When a caller passes a remaining length of zero, the guard correctly returns `NX_SECURE_X509_ASN1_LENGTH_TOO_LONG`, but the read has already happened one byte past the end of the buffer. code: nx_secure/src/nx_secure_x509_asn1_tlv_block_parse.c ``` UINT _nx_secure_x509_asn1_tlv_block_parse(const UCHAR *buffer, ULONG *buffer_length, USHORT *tlv_type, USHORT *tlv_tag_class, ULONG *tlv_length, const UCHAR **tlv_data, ULONG *header_length) { UINT current_index; USHORT current_tag; ULONG length; ULONG length_bytes; current_index = 0; current_tag = buffer[current_index]; /* <-- read before the bounds check */ if (*buffer_length < 1) { return(NX_SECURE_X509_ASN1_LENGTH_TOO_LONG); } ``` The remainder of the function is correctly ordered. The multi-byte length path is guarded by `length_bytes > 4 || length_bytes > *buffer_length` before its read loop, the decoded value is checked against `length > *buffer_length`, and the second single-byte length read follows its own `*buffer_length < 1` guard. The tag read is the only load placed ahead of its check.
Affected software
Eclipse Foundation
NetX Duo
pkg:github/eclipse-threadx/netxduoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The _nx_secure_x509_asn1_tlv_block_parse() function in NetX Duo parses ASN.1 TLV blocks from DER-encoded data used in X.509 certificate parsing. It reads the ASN.1 tag byte from the buffer before checking if the buffer length is at least one byte, leading to a buffer over-read (CWE-126) when the buffer length is zero. Subsequent length checks in the function are correctly implemented, but the initial tag read occurs out-of-bounds. This vulnerability affects versions from 0 up to and including 6.5.1.202602 of NetX Duo.
Potential Impact
This buffer over-read vulnerability could cause the function to read memory beyond the provided buffer, potentially leading to application crashes or information disclosure depending on how the parsed data is used. The vulnerability occurs during TLS handshake certificate parsing, which may impact the security or stability of TLS connections using NetX Duo. No known exploits are reported in the wild at this time.
Mitigation Recommendations
No vendor advisory or patch information is provided for this vulnerability. Patch status is not yet confirmed — check the Eclipse Foundation or NetX Duo vendor advisories for current remediation guidance. Until a fix is available, users should consider mitigating exposure by validating input buffers before passing them to the vulnerable function or applying any recommended vendor mitigations once published.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- eclipse
- Date Reserved
- 2026-09-29T16:21:58.057Z
- State
- PUBLISHED
Threat ID: 6abbf57794a11e1e08e480d0
Added to database: 09/29/2026, 17:29:27 UTC
Last enriched: 09/29/2026, 17:40:43 UTC
Last updated: 09/29/2026, 18:21:05 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.