dbcve.org
Threadx UsbxApplication · Eclipse

CVE-2023-48697

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 memory buffer and pointer vulnerabilities in Azure RTOS USBX. The affected components include functions/processes in pictbridge and host class, related to PIMA, storage, CDC ACM, ECM, audio, hub 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 memory buffer and pointer vulnerabilities in pictbridge and host class components (PIMA, storage, CDC ACM, ECM, audio, hub) allowing remote code execution. Affected versions are RTOS v6.2.1 and below. The vulnerability is due to improper memory handling in the USB stack processing.

MitigationUpgrade to USBX release 6.3.0 or later. No workarounds exist; this is a critical RCE vulnerability requiring immediate attention.

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 in your firmware or library
    Search for USBX version strings or version macros in your codebase. Look for definitions like UX_VERSION_STRING, UX_HARDWARE_VERSION, or check build artifacts, release notes, or firmware metadata that reference the ThreadX USBX library version.
    Affected if The installed version is 6.2.1 or below, or the version cannot be determined and is assumed to be older than 6.3.0
  2. Verify if pictbridge functionality is compiled or enabled
    Check your build configuration or source files for inclusion of pictbridge-related code. Look for references to UX_PICTBRIDGE, pictbridge class initialization functions, or the pictbridge component in your USB stack configuration.
    Affected if Pictbridge support is enabled in the build
  3. Determine if PIMA (PTP/MTP) host class is in use
    Search for PIMA class usage in your USB host implementation. Look for UX_HOST_CLASS_PIMA initialization, pima_*.c source files, or build flags enabling the PIMA mass storage class.
    Affected if The PIMA host class component is compiled or configured
  4. Check if USB storage host class is enabled
    Examine your USB host stack configuration for storage class support. Look for UX_HOST_CLASS_STORAGE references, storage class initialization code, or build options enabling USB mass storage functionality.
    Affected if USB storage host class is enabled
  5. Identify if CDC ACM, ECM, audio, or hub host classes are present
    Review your USBX host class configuration for any of the following: CDC ACM (UX_HOST_CLASS_CDC_ACM), ECM (UX_HOST_CLASS_ECM), audio (UX_HOST_CLASS_AUDIO), or hub (UX_HOST_CLASS_HUB). Check build configurations and included source files.
    Affected if Any of the CDC ACM, ECM, audio, or hub host class components are compiled or configured

You are affected if your USBX version is 6.2.1 or below AND you have any of the pictbridge, PIMA, storage, CDC ACM, ECM, audio, or hub host class components enabled in your build.

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 to USBX release 6.3.0 or later. No workarounds exist; this is a critical RCE vulnerability requiring immediate attention.

Recommended fix High confidence

USBX 6.3.0

  1. Identify the current Azure RTOS USBX version in use by reviewing project dependencies or firmware version information
  2. Download Azure RTOS USBX version 6.3.0 or later from the official Microsoft Azure RTOS repository
  3. Replace the existing USBX library files in the project with the updated version 6.3.0 files
  4. Rebuild and recompile the firmware/application with the new USBX library
  5. Deploy the updated firmware to devices
  6. Verify USB functionality (device host, OTG, pictbridge, PIMA, storage, CDC ACM, ECM, audio, hub) operates correctly after the update

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

Fix this in Threadx Usbx Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing20.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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