dbcve.org
Threadx Netx DuoApplication · Eclipse

CVE-2025-55092

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-17
Fix available
A fix is available. Upgrade to 6.4.4.202503 or later.
See remediation →
62/100
Remediation priority · Elevated
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
In Eclipse Foundation NetX Duo before 6.4.4, the networking support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _nx_ipv4_option_process() when processing an IPv4 packet with the timestamp option.

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 confidence

Eclipse Foundation NetX Duo before 6.4.4 contains an out-of-bounds read vulnerability in the _nx_ipv4_option_process() function when processing IPv4 packets containing the timestamp option. This occurs due to insufficient bounds checking when parsing the timestamp option in IPv4 packets, potentially allowing an attacker to read adjacent memory beyond the packet buffer.

MitigationUpdate NetX Duo to version 6.4.4 or later, which contains the fix for the out-of-bounds read in _nx_ipv4_option_process(). For systems that cannot update immediately, implement network filtering at perimeter devices to drop malformed IPv4 packets with suspicious timestamp options.

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.4.202503

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
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 checks

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

  1. Identify if NetX Duo is in use
    Review your project dependencies or firmware build configuration to confirm Eclipse ThreadX NetX Duo network stack is included
    Affected if NetX Duo is present in the system
  2. Determine NetX Duo version
    Check the version number from your NetX Duo library binary, header file (such as nx_port.h or nx_api.h), or build manifest. Compare against the affected range: versions prior to 6.4.4.202503
    Affected if Installed version is earlier than 6.4.4.202503
  3. Verify IPv4 is enabled
    Inspect your NetX Duo configuration (typically in nx_user.h or build-time configuration) for NX_ENABLE_IPV4 being defined or set to 1
    Affected if IPv4 support (NX_ENABLE_IPV4) is enabled
  4. Confirm IPv4 packet processing is active
    Check if your application initializes IPv4 and processes incoming IPv4 packets using NX interface APIs
    Affected if The device processes IPv4 network traffic
  5. Check if timestamp option handling is reachable
    Examine network packet flow to determine whether IPv4 packets with timestamp options can reach the _nx_ipv4_option_process() function. This may require reviewing firewall rules, packet filters, or network edge configuration.
    Affected if IPv4 packets with timestamp options can reach the NetX Duo stack

You are affected if your system uses Eclipse ThreadX NetX Duo versions earlier than 6.4.4.202503 with IPv4 processing enabled and IPv4 packets containing timestamp options can reach the vulnerable function.

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.4.202503 or later
Fixed in 6.4.4.202503
Interim mitigation

Update NetX Duo to version 6.4.4 or later, which contains the fix for the out-of-bounds read in _nx_ipv4_option_process(). For systems that cannot update immediately, implement network filtering at perimeter devices to drop malformed IPv4 packets with suspicious timestamp options.

Recommended fix Moderate confidence

NetX Duo 6.4.4.202503 or later

  1. 1. Identify all products and devices using NetX Duo networking stack with versions prior to 6.4.4.202503
  2. 2. Obtain the latest stable release of NetX Duo version 6.4.4.202503 or later from the Eclipse Foundation
  3. 3. Review the release notes and changelog for version 6.4.4.202503 to confirm the _nx_ipv4_option_process() vulnerability fix is included
  4. 4. Update the NetX Duo library in all affected products to version 6.4.4.202503 or newer
  5. 5. Rebuild and recompile the ThreadX RTOS application with the updated NetX Duo library
  6. 6. Test the updated firmware/software to ensure network functionality remains intact, particularly IPv4 packet processing with timestamp options
  7. 7. Deploy the updated firmware to all affected devices
Caveat Review release notes for any API changes or behavioral differences between your current version and 6.4.4.202503

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55092 — 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-55092 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