dbcve.org
Threadx UsbxApplication · Eclipse

CVE-2023-48698

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 vulnerabilities in Azure RTOS USBX. The affected components include functions/processes in host stack and host classes, related to device linked classes, GSER and HID 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 expired pointer dereference vulnerabilities in the host stack and host classes (specifically GSER and HID device linked classes), allowing remote code execution. This affects versions 6.2.1 and below.

MitigationUpgrade to USBX release 6.3.0 or later; no workarounds are available.

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 installation
    Locate the USBX library or header files in your embedded system firmware. USBX is typically distributed as part of Azure RTOS or Eclipse ThreadX. Search for files containing 'usbx', 'ux_api.h', or 'ux.h' in your codebase or firmware image.
    Affected if USBX code or libraries are present in your environment
  2. Determine USBX version
    Inspect version information in USBX header files (e.g., UX_VERSION_MAJOR, UX_VERSION_MINOR in ux_api.h or ux.h), or check the release notes/changelog included with the USBX distribution. Compare the version number to 6.3.0.
    Affected if The installed version is below 6.3.0 (e.g., 6.2.1, 6.2.0, 6.1.x, or earlier)
  3. Verify USBX host mode is enabled
    Examine your USBX configuration (typically in ux_user.h, tx_api.h, or custom configuration files). Look for compile-time defines such as UX_HOST_STACKERATION or UX_DEVICE_CLASS_ENABLE that indicate host mode is active.
    Affected if USBX host mode functionality is compiled into your build
  4. Check for GSER or HID device class usage
    Review your application code for inclusion of GSER (generic serial) or HID (Human Interface Device) class headers and initialization calls, such as ux_host_class_gser_... or ux_host_class_hid_... functions.
    Affected if Your system uses the GSER or HID host classes for USB device communication

You are affected if your environment contains Eclipse ThreadX USBX versions below 6.3.0 with USBX host mode and GSER or HID host classes enabled.

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

Recommended fix High confidence

USBX 6.3.0

  1. Upgrade Azure RTOS USBX to version 6.3.0 or later
  2. Verify the upgrade by reviewing the USBX release notes for version 6.3.0
  3. Test the updated USBX implementation in your development environment before deploying to production

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

Fix this in Threadx Usbx Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,240
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,584.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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