dbcve.org
Threadx UsbxApplication · Eclipse

CVE-2023-48694

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 expired pointer dereference and type confusion vulnerabilities in Azure RTOS USBX. The affected components include functions/processes in host stack and host class, related to device linked classes, ASIX, Prolific, SWAR, audio, CDC ECM 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 versions 6.2.1 and below contain critical vulnerabilities (expired pointer dereference and type confusion) in the host stack and host class components, specifically affecting device-linked classes including ASIX, Prolific, SWAR, audio, and CDC ECM. These memory safety flaws allow remote code execution due to improper memory management during USB device interactions.

MitigationUpgrade Azure RTOS USBX to version 6.3.0 or later to address the expired pointer dereference and type confusion vulnerabilities. No workarounds are available; immediate patching is required given the critical severity.

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 version
    Locate the USBX version definition in your codebase (check version header files, build configuration, or release documentation). Common locations include ux_version.h or version.c within the USBX source directory.
    Affected if The installed version is 6.2.1 or below, or any version prior to 6.3.0
  2. Verify host stack is enabled
    Examine your USBX configuration (typically ux_user.h or ux_config.h) and confirm that USBX host mode is enabled via UX_HOST_STACK_INITIALIZATION or equivalent configuration macro.
    Affected if UX_HOST_STACK_INITIALIZATION or host mode is defined/enabled in your configuration
  3. Check for affected device class inclusion
    Review your build configuration or source files to determine if any of the following device-linked classes are compiled in: ASIX, Prolific, SWAR, audio, or CDC ECM. Look for corresponding class initialization calls (e.g., ux_host_class_asix_init, ux_host_class_cdc_ecm_init).
    Affected if Any of the affected classes (ASIX, Prolific, SWAR, audio, CDC ECM) are present in the build
  4. Confirm device class is actively used
    Inspect your application code to verify if the affected USB host classes are actually instantiated or used at runtime, rather than just compiled in.
    Affected if The vulnerable class is instantiated and actively handling USB device interactions

You are affected if your USBX version is below 6.3.0 AND the host stack with any of the vulnerable device classes (ASIX, Prolific, SWAR, audio, CDC ECM) is enabled and in use.

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 to address the expired pointer dereference and type confusion vulnerabilities. No workarounds are available; immediate patching is required given the critical severity.

Recommended fix High confidence

USBX 6.3.0

  1. Upgrade Azure RTOS USBX to version 6.3.0 or later to address the expired pointer dereference (CWE-825) vulnerability

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

Fix this in Threadx Usbx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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