dbcve.org
Threadx Netx DuoApplication · Eclipse

CVE-2025-55091

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to 6.4.4.202503 or later.
See remediation →
74/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 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_ip_packet_receive() function when received an Ethernet with type set as IP but no IP data.

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

An out-of-bounds read vulnerability exists in the _nx_ip_packet_receive() function in NetX Duo before version 6.4.4. The vulnerability is triggered when the function processes an Ethernet frame with type set to IP (0x0800) but containing no actual IP data, causing the function to read beyond the packet buffer bounds.

MitigationUpgrade NetX Duo to version 6.4.4 or later which contains the bounds checking fix for this vulnerability.

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
Low

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

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 the NetX Duo library version
    Locate the NetX Duo library or header files in your deployment and check for version defines such as NX_DUEO_VERSION_MAJOR, NX_DUO_VERSION_MINOR, or NX_VERSION macros. If NetX Duo is linked as a binary library, check the library file metadata or contact your vendor for the exact version string.
    Affected if The version is lower than 6.4.4.202503 (e.g., 6.4.3, 6.3.x, or earlier releases).
  2. Verify IP packet receive processing is enabled
    Inspect your NetX Duo configuration (typically in a header file like nx_user.h or a custom configuration header) for the definition NX_INCLUDE_IP_RECEIVE or related IP receive functionality macros. Also check if your application initializes IP instances via nx_ip_create() or nx_ip_initialize().
    Affected if IP packet processing is enabled and your device accepts incoming Ethernet frames.
  3. Confirm exposure to untrusted network traffic
    Review your network interface configuration to determine if the device is directly exposed to untrusted networks or can receive Ethernet frames from external sources. Check if there are firewall rules or network segmentation that limit which hosts can send traffic to the device.
    Affected if The device can receive raw Ethernet frames from untrusted sources on port or interface that NetX Duo monitors for IP traffic.
  4. Check for recent security updates
    Review your software Bill of Materials (SBOM), vendor release notes, or patch history to see if a security update addressing CVE-2025-55091 has been applied to your NetX Duo component.
    Affected if No patch for CVE-2025-55091 has been applied and the version remains below 6.4.4.202503.

Your environment is affected if NetX Duo version is below 6.4.4.202503 AND your device processes incoming IP-type Ethernet frames from potentially untrusted network sources.

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

Upgrade NetX Duo to version 6.4.4 or later which contains the bounds checking fix for this vulnerability.

Recommended fix Moderate confidence

6.4.4.202503

  1. 1. Identify all instances of ThreadX NetX Duo in your deployment that are running versions prior to 6.4.4.202503
  2. 2. Obtain the ThreadX NetX Duo 6.4.4.202503 or later release from the official Eclipse Foundation distribution channels
  3. 3. Review the release notes and changelog for version 6.4.4 to understand any changes relevant to your implementation
  4. 4. In a testing environment, replace the NetX Duo library binary with version 6.4.4.202503 or newer
  5. 5. Test your application's networking functionality, particularly Ethernet packet reception and IP packet processing
  6. 6. Verify that the _nx_ip_packet_receive() function handles malformed packets correctly (Ethernet frames with IP type but no IP data)
  7. 7. If all tests pass, deploy the updated NetX Duo library to production environments

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

Fix this in Threadx Netx Duo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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