dbcve.org
Azure Rtos Netx DuoOperating system · Microsoft

CVE-2023-48692

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-05
Fix available
A fix is available. Upgrade to 6.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Azure RTOS NetX Duo is a TCP/IP network stack designed specifically for deeply embedded real-time and IoT applications. An attacker can cause remote code execution due to memory overflow vulnerabilities in Azure RTOS NETX Duo. The affected components include processes/functions related to icmp, tcp, snmp, dhcp, nat and ftp in RTOS v6.2.1 and below. The fixes have been included in NetX Duo release 6.3.0. Users are advised to upgrade. There are no known workarounds for 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 · high confidence

Memory overflow (buffer overflow) vulnerabilities in multiple network protocol components (ICMP, TCP, SNMP, DHCP, NAT, FTP) of Azure RTOS NetX Duo allow remote attackers to achieve remote code execution. The vulnerabilities exist in versions 6.2.1 and below.

MitigationUpgrade Azure RTOS NetX Duo to release 6.3.0 or later. No workarounds are available.

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
Azure Rtos Netx DuoOperating system
Affected:< 6.3.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if Azure RTOS NetX Duo is in use
    Review the firmware or software bill of materials (BOM) for the presence of the NetX Duo network stack library or header files (nx_api.h, nx_ip.h, etc.)
    Affected if NetX Duo is found in the firmware or software components
  2. Determine the installed NetX Duo version
    Check the version constant in the NetX Duo header file (typically nx_api.h) or the library version metadata included in the firmware; common version macros include NX_VERSION_MAJOR, NX_VERSION_MINOR, NX_VERSION_PATCH
    Affected if The version is 6.2.1 or below, or the version cannot be determined but is known to be older than 6.3.0
  3. Check if ICMP protocol support is enabled
    Inspect the NetX Duo configuration options in the build; look for NX_ENABLE_ICMP, NX_ICMP_ENABLE, or similar ICMP-related defines in the project configuration or header files
    Affected if ICMP is enabled and NetX Duo version is 6.2.1 or below
  4. Check if TCP protocol support is enabled
    Inspect the NetX Duo configuration for TCP-related options (NX_ENABLE_TCP, NX_TCP_ENABLE) in the project configuration or header files; verify if the TCP component is compiled into the firmware
    Affected if TCP is enabled and NetX Duo version is 6.2.1 or below
  5. Check if SNMP protocol support is enabled
    Inspect the NetX Duo configuration for SNMP options (NX_ENABLE_SNMP, NX_SNMP_ENABLE) in the project configuration or header files; verify if SNMP service is included in the build
    Affected if SNMP is enabled and NetX Duo version is 6.2.1 or below
  6. Check if DHCP, NAT, or FTP protocols are enabled
    Inspect NetX Duo configuration for DHCP (NX_ENABLE_DHCP), NAT (NX_ENABLE_NAT), or FTP (NX_ENABLE_FTP) options in the project configuration or header files; verify if these services are compiled into the firmware
    Affected if Any of DHCP, NAT, or FTP are enabled and NetX Duo version is 6.2.1 or below

The system is affected if it runs Azure RTOS NetX Duo version 6.2.1 or below AND has any of the affected network protocols (ICMP, TCP, SNMP, DHCP, NAT, or FTP) enabled in the firmware configuration.

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.3.0 or later
Fixed in 6.3.0
Interim mitigation

Upgrade Azure RTOS NetX Duo to release 6.3.0 or later. No workarounds are available.

Recommended fix High confidence

NetX Duo 6.3.0

  1. Identify all deployments and devices using Azure RTOS NetX Duo versions prior to 6.3.0
  2. Locate the official Microsoft Azure RTOS NetX Duo 6.3.0 release from the Microsoft repository
  3. Replace the current NetX Duo library/binary with version 6.3.0 in all affected deployments
  4. Ensure components using icmp, tcp, snmp, dhcp, nat, and ftp are updated to the new version
  5. Rebuild and redeploy the firmware/images for all affected embedded devices
  6. Verify the upgrade was successful and the system functions correctly

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

Fix this in Azure Rtos Netx Duo Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing32.0 h
  • Review / QA16.0 h
80.0 hours of engineering $13,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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