Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-55082: CWE-125 Out-of-bounds Read in Eclipse Foundation NetX Duo

0
Medium
VulnerabilityCVE-2025-55082cvecve-2025-55082cwe-125
Published: Wed Oct 15 2025 (10/15/2025, 11:03:31 UTC)
Source: CVE Database V5
Vendor/Project: Eclipse Foundation
Product: NetX Duo

Description

In NetX Duo version before 6.4.4, the component of Eclipse Foundation ThreadX, there was a potential out of bound read in _nx_secure_tls_process_clienthello() because of a missing validation of PSK length provided in the user message.

AI-Powered Analysis

AILast updated: 10/15/2025, 11:28:45 UTC

Technical Analysis

CVE-2025-55082 is a vulnerability identified in the Eclipse Foundation's NetX Duo, a widely used embedded TCP/IP stack, specifically in versions prior to 6.4.4. The flaw resides in the _nx_secure_tls_process_clienthello() function, which processes the TLS ClientHello message during the handshake phase. The vulnerability is caused by a missing validation of the Pre-Shared Key (PSK) length field provided by the client. This improper validation leads to an out-of-bounds read (CWE-125), where the software reads memory beyond the intended buffer boundaries. Such out-of-bounds reads can cause information disclosure by leaking sensitive memory contents or potentially trigger application crashes due to memory access violations. The CVSS 4.0 base score is 6.9 (medium severity), reflecting that the vulnerability can be exploited remotely over the network without requiring authentication or user interaction. The attack vector is network-based (AV:N), with low attack complexity (AC:L), and no privileges or user interaction needed (PR:N/UI:N). The impact is limited to confidentiality (VC:L) with no impact on integrity or availability. No known exploits are currently reported in the wild, but the vulnerability poses a risk to embedded devices and IoT systems that rely on NetX Duo for secure communications. The lack of patch links indicates that users should monitor the Eclipse Foundation's advisories for updates. This vulnerability highlights the importance of strict input validation in TLS handshake processing within embedded networking stacks.

Potential Impact

For European organizations, the impact of CVE-2025-55082 is primarily related to confidentiality breaches in embedded and IoT devices that use vulnerable versions of NetX Duo. These devices are often found in industrial automation, telecommunications, smart infrastructure, and critical control systems. An attacker exploiting this vulnerability could remotely read sensitive memory contents, potentially exposing cryptographic keys, credentials, or other confidential data. While the vulnerability does not directly affect system integrity or availability, leaked information could facilitate further attacks or espionage. European industries with extensive use of embedded systems, such as manufacturing plants, energy grids, and telecom providers, could face increased risk of intellectual property theft or disruption of secure communications. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits targeting these embedded environments. Therefore, the vulnerability could undermine trust in secure communications and data confidentiality in critical sectors across Europe.

Mitigation Recommendations

To mitigate CVE-2025-55082, organizations should immediately identify all devices and systems using NetX Duo versions prior to 6.4.4. The primary mitigation is to upgrade to NetX Duo version 6.4.4 or later, where the PSK length validation issue has been addressed. If immediate patching is not feasible, organizations should implement network-level controls to restrict access to vulnerable devices, such as firewall rules limiting TLS handshake traffic to trusted sources. Additionally, monitoring network traffic for anomalous TLS ClientHello messages with irregular PSK lengths can help detect exploitation attempts. Embedded device manufacturers should review their TLS handshake implementations to ensure strict validation of all input fields, particularly PSK lengths. Security teams should also conduct penetration testing and code audits on embedded systems to identify similar input validation weaknesses. Finally, maintaining an up-to-date inventory of embedded devices and their software versions will facilitate rapid response to such vulnerabilities in the future.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
eclipse
Date Reserved
2025-08-06T18:32:14.666Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ef81e7290e66ee3b3a9f55

Added to database: 10/15/2025, 11:13:43 AM

Last enriched: 10/15/2025, 11:28:45 AM

Last updated: 10/15/2025, 2:17:20 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats