CVE-2025-55090
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 before 6.4.4, the networking support module for Eclipse Foundation ThreadX, there was a potential out of bound read issue in _nx_ipv4_packet_receive() function when received an Ethernet frame with less than 4 bytes of IP packet.
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 confidenceNetX Duo before 6.4.4 contains an out-of-bounds read vulnerability in the _nx_ipv4_packet_receive() function. When processing an Ethernet frame containing an IP packet with fewer than 4 bytes of data, the function attempts to read IP header fields without validating that sufficient bytes are present, leading to a read beyond the buffer boundary.
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.4.202503CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the NetX Duo version in your environmentLocate the NetX Duo library or header files and check the version definition, typically found in nx_api.h or release notesAffected if The installed version is lower than 6.4.4.202503
-
Confirm IPv4 packet reception is enabledCheck your NetX Duo configuration (usually in tx_user.h or netxduo.h) for NX_INCLUDE_IPV4 or NX_IP_V4 compilation flagsAffected if IPv4 support (NX_INCLUDE_IPV4) is enabled in your build
-
Verify your application uses the IP packet receive pathSearch your code for calls to nx_ip_raw_packet_receive or other IP receive functions that trigger _nx_ipv4_packet_receiveAffected if Your application or stack processes incoming IPv4 packets via the raw packet receive path
-
Determine if the device accepts external network inputReview your network configuration for NX_ENABLE_IP_RAW_PACKET_FILTER or similar settings that allow processing of external Ethernet framesAffected if Your system accepts and processes inbound Ethernet frames containing IP packets from external sources
You are affected if your NetX Duo version is below 6.4.4.202503, IPv4 is enabled, and your device processes incoming IPv4 packets from untrusted network sources.
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 · scoped6.4.4.202503
Upgrade NetX Duo to version 6.4.4 or later. Alternatively, implement input validation in _nx_ipv4_packet_receive() to verify the IP packet contains at least 4 bytes before attempting to read IP header fields.
NetX Duo 6.4.4 (or 6.4.4.202503)
- 1. Identify the current NetX Duo version in use by checking the library version or build configuration
- 2. Obtain NetX Duo version 6.4.4.202503 or later from the official Eclipse Foundation ThreadX repository
- 3. Replace the vulnerable NetX Duo library/binary with the fixed version in your project
- 4. Rebuild the firmware or application using the updated NetX Duo library
- 5. Verify the build completes successfully and test the device/firmware to ensure normal network operations function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55090 — 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-55090 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