CVE-2025-55082
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn NetX Duo versions before 6.4.4, the TLS client hello processing function _nx_secure_tls_process_clienthello() lacks proper validation of the Pre-Shared Key (PSK) length field from incoming client messages. This missing bounds check allows an attacker to trigger an out-of-bounds read vulnerability by providing a malformed PSK length value, potentially leading to information disclosure or denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 6.4.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify NetX Duo version in useCheck your project's dependency files (like package.json, composer.json, requirements.txt, or library manifests) for the NetX Duo library version, or inspect the nx_secure.h header file if present in your codebase to find the NetX Duo version definitionAffected if The version listed is 6.4.3 or lower
-
Verify TLS is enabledSearch your NetX Duo configuration (nx_api.h, nx_user.h, or custom configuration files) for NX_SECURE_ENABLE definitions, or check if your application code includes TLS-related headers such as nx_secure_tls.hAffected if TLS functionality is enabled in the build configuration
-
Confirm TLS client role is in useInspect your application code for instances of nx_secure_tls_client_session_create or similar TLS client initialization functions, or check if the product acts as a TLS client accepting incoming connectionsAffected if The device or application functions as a TLS client that processes incoming ClientHello messages
-
Check if PSK cipher suites are enabledLook for NX_SECURE_PSK_CIPHERSUITE or similar pre-shared key related definitions in your NetX Duo configuration files, or search for psk_identity and psk_secret configuration usage in your TLS setup codeAffected if PSK (Pre-Shared Key) cipher suites are defined or configured in your TLS implementation
Your environment is affected if you are using NetX Duo version 6.4.3 or earlier with TLS enabled and the device operates as a TLS client that processes ClientHello messages, particularly if PSK cipher suites are in use.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade NetX Duo to version 6.4.4 or later, which includes proper validation of PSK length before use in memory operations.
NetX Duo 6.4.4
- Upgrade ThreadX NetX Duo to version 6.4.4 or later to address the missing PSK length validation vulnerability in _nx_secure_tls_process_clienthello()
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55082 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data