dbcve.org
Threadx Netx DuoApplication · Eclipse

CVE-2025-55102

HIGH · 7.5 CVSS v3.1 Published 2026-01-27
Fix available
A fix is available. Upgrade to 6.4.5.202504 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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 a malicious packet to trigger this vulnerability.

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 · moderate confidence

A denial-of-service vulnerability exists in Eclipse ThreadX NetX Duo's IPv6 component. Specially crafted ICMPv6 'Packet Too Big' messages containing more than 15 different source addresses can trigger the vulnerability, likely causing resource exhaustion or processing loop leading to system denial of service.

MitigationApply vendor patches for Eclipse ThreadX NetX Duo when available; implement network-level filtering or rate-limiting for ICMPv6 'Packet Too Big' messages with excessive source addresses as a compensating control.

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
Threadx Netx DuoApplication
Affected:< 6.4.5.202504

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NetX Duo usage
    Locate the NetX Duo library or check firmware/components that depend on Eclipse ThreadX NetX Duo. In embedded systems, this may be a compiled library (nx*.a, nx*.lib) or part of the firmware image.
    Affected if The system uses Eclipse ThreadX NetX Duo as its network stack
  2. Check NetX Duo version
    Retrieve the version information from the NetX Duo library file or build system. Common methods: examine the library filename containing version, check version macros in headers (e.g., NX_VERSION_MAJOR/NX_VERSION_MINOR), or query via API nx_system_version_get() if available.
    Affected if The installed version is earlier than 6.4.5.202504 (e.g., 6.4.4, 6.3.x, etc.)
  3. Verify IPv6 is enabled
    Check NetX Duo configuration: examine the build configuration file or #define statements for NX_ENABLE_IPV6 or NX_IPV6_ENABLED set to 1. In runtime, verify via API call nx_ip_status_check() with NX_IPV6_ENABLED status.
    Affected if IPv6 support is enabled in the NetX Duo configuration (required for the attack surface)
  4. Confirm ICMPv6 processing is active
    Check if ICMPv6 is enabled via NX_ENABLE_ICMPV6 or NX_ICMPv6_ENABLE configuration. Additionally, verify the device has an IPv6 address assigned (active IPv6 interface) which is necessary for receiving ICMPv6 'Packet Too Big' messages.
    Affected if ICMPv6 is enabled and the device has an active IPv6 interface

A system is affected if it runs a version of Eclipse ThreadX NetX Duo earlier than 6.4.5.202504 with IPv6 and ICMPv6 enabled, and the device can receive ICMPv6 messages on its IPv6 interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.4.5.202504 or later
Fixed in 6.4.5.202504
Interim mitigation

Apply vendor patches for Eclipse ThreadX NetX Duo when available; implement network-level filtering or rate-limiting for ICMPv6 'Packet Too Big' messages with excessive source addresses as a compensating control.

Recommended fix High confidence

Eclipse ThreadX NetX Duo version 6.4.5.202504 or later

  1. 1. Identify the current Eclipse ThreadX NetX Duo version in use by checking the build configuration or library manifest
  2. 2. Obtain Eclipse ThreadX NetX Duo version 6.4.5.202504 or later from the official Eclipse Foundation distribution (download.eclipse.org/threadx) or your vendor's software distribution
  3. 3. Replace the existing NetX Duo library binary with the updated version 6.4.5.202504 or newer
  4. 4. Rebuild the firmware/application with the updated NetX Duo library
  5. 5. Test the IPv6 functionality to ensure normal operation after the upgrade
  6. 6. Verify that the 'Packet Too Big' ICMPv6 message handling no longer causes uncontrolled resource consumption
Caveat Review Eclipse ThreadX NetX Duo release notes for version 6.4.5.202504 to check for any API changes or behavioral differences in IPv6 functionality that may affect your application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Threadx Netx Duo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55102 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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