VulnerabilityPublished 5 Dec 2023Updated 29 May 2025

CVE-2023-48695: azure-rtos usbx · Out-of-bounds Write

Affects azure-rtos usbxSource CVE Database V5

Not known to be exploited · CVSS 7.2 High : upgrade to 6.3.0 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.3.0

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade azure-rtos/usbx to 6.3.0.

Affected software

Product	Affected	Fixed in
GitHubazure-rtos/usbx`pkg:github/azure-rtos/usbx`Other threats	Affected <6.3.0	Fixed in 6.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate upgrade to Azure RTOS USBX version 6.3.0 or later is critical to remediate the vulnerability.
Conduct an inventory of embedded devices and systems using Azure RTOS USBX, focusing on versions prior to 6.3.0, to identify at-risk assets.
Implement strict physical security controls to limit unauthorized access to USB ports on embedded devices, including port blocking or disabling unused USB interfaces where feasible.
Employ network segmentation to isolate embedded systems from critical enterprise networks, reducing the risk of lateral movement if a device is compromised.
Monitor device logs and network traffic for anomalous USB activity or unexpected communications that could indicate exploitation attempts.
Collaborate with device vendors and suppliers to ensure timely firmware updates and security patches are applied.
For devices that cannot be immediately patched, consider deploying compensating controls such as USB traffic filtering or endpoint detection solutions tailored for embedded environments.
Incorporate this vulnerability into organizational risk assessments and incident response plans to prepare for potential exploitation scenarios.

Description

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS ThreadX. An attacker can cause remote code execution due to out of bounds write vulnerabilities in Azure RTOS USBX. The affected components include functions/processes in host and device classes, related to CDC ECM and RNDIS in RTOS v6.2.1 and below. The fixes have been included in USBX release 6.3.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Impact

For European organizations, the impact of CVE-2023-48695 can be substantial, particularly for industries relying on embedded systems that incorporate Azure RTOS USBX, such as industrial automation, medical devices, automotive systems, and telecommunications infrastructure. Successful exploitation could lead to unauthorized control over embedded devices, data breaches, or disruption of critical services. Given the integration of Azure RTOS in many IoT and edge devices, attackers could leverage this vulnerability to pivot into internal networks, compromising confidentiality and integrity of sensitive information. The lack of user interaction and privilege requirements lowers the barrier for exploitation once physical or network access to USB interfaces is obtained. This is especially concerning for sectors with stringent regulatory requirements like healthcare and finance in Europe. Additionally, the vulnerability could be exploited in supply chain attacks targeting embedded device manufacturers or service providers. The absence of known exploits currently provides a window for proactive mitigation, but the high severity score underscores the urgency for European organizations to assess and remediate affected systems promptly.

CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/azure-rtos/usbx/security/advisories/GHSA-mwj9-rpph-v8wc (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 03:27 UTC

WeaknessesCWE-787

Technical details

References

Community reviews

Related threats