Skip to content
Fencer Vulns
critical 9.1

CVE-2023-48692 json

Azure RTOS NetX Duo Remote Code Execution Vulnerability

published 2023-12-05 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-52736

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

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.

Patch / fix

  • microsoft azure_rtos_netx_duo 6.3.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-25-226-25 updated cvss 9.8

Rockwell Automation Micro800

  • Rockwell Automation PLC Micro820 LC20 <V14.011 Rockwell Automation PLC Micro850 L50E >=V20.011, <=V22.011 Rockwell Automation PLC Micro850 LC50 <V12.013 Rockwell Automation PLC Micro870 L70E >=V20.011, <=V22.011 Rockwell Automation PLC Micro870 LC70 <V12.013
    affected: vendor fix, mitigation “Rockwell Automation recommends the following updates:” rockwellautomation.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

3.11% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • azure-rtos netxduo

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.