dbcve.org
Threadx UsbxApplication · Eclipse

CVE-2023-48695

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 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.

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

Azure RTOS USBX contains out-of-bounds write vulnerabilities in CDC ECM and RNDIS host/device class functions. These memory corruption flaws allow remote attackers to execute arbitrary code by sending specially crafted USB requests, potentially compromising the entire embedded device.

MitigationUpgrade Azure RTOS USBX to version 6.3.0 or later. No workarounds exist; the vulnerable USBX library must be updated in the firmware/embedded system.

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 UsbxApplication
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 USBX library presence
    Examine the firmware binary, build artifacts, or source code for the presence of Azure RTOS USBX (ThreadX USBX) library files or string identifiers such as 'USBX', 'ux_api.h', or related USBX header/source files.
    Affected if USBX library is found in the firmware or software stack
  2. Determine installed USBX version
    Locate the USBX version definition in the source code (typically in a version header or ux_version.h) or inspect the compiled library binary for version metadata. Compare against the reported version string or number.
    Affected if The identified version is less than 6.3.0 (e.g., 6.2.x, 6.1.x, 6.0.x, or any pre-6.3.0 release)
  3. Check if CDC ECM class is enabled
    Review the build configuration (e.g., threadx.h, ux_system_initialize.c, or project defines) for CDC ECM class compilation or usage. Look for configuration flags such as UX_INCLUDE_CDC_ECM_CLASS, UX_HOST_CLASS_CDC_ECM_ENABLE, or UX_DEVICE_CLASS_CDC_ECM_ENABLE.
    Affected if CDC ECM host or device class is compiled into the firmware and the USBX version is below 6.3.0
  4. Check if RNDIS class is enabled
    Review the build configuration for RNDIS class compilation or usage. Look for configuration flags such as UX_INCLUDE_RNDIS_CLASS, UX_HOST_CLASS_RNDIS_ENABLE, or UX_DEVICE_CLASS_RNDIS_ENABLE.
    Affected if RNDIS host or device class is compiled into the firmware and the USBX version is below 6.3.0

The environment is affected if Azure RTOS USBX version is below 6.3.0 AND either the CDC ECM or RNDIS class function is enabled in the firmware.

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 USBX to version 6.3.0 or later. No workarounds exist; the vulnerable USBX library must be updated in the firmware/embedded system.

Recommended fix High confidence

USBX release 6.3.0

  1. Obtain Azure RTOS USBX version 6.3.0 from the official Microsoft repository or distribution channel
  2. Replace the existing USBX library in your project with the version 6.3.0
  3. Rebuild and redeploy the firmware/application with the updated USBX library
  4. Verify the CDC ECM and RNDIS functionality operates correctly after the upgrade

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

Fix this in Threadx Usbx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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