Cyber Resilience

CVE-2023-48696

Eclipse Threadx Usbx ≤ 6.3.0

Published
05 December 2023
Modified
27 October 2025
CVSS Score v3.1 6.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
EPSS Score 0.0095 58th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2023-48696 is a medium-severity Improper Check for Unusual or Exceptional Conditions (CWE-754) vulnerability in Eclipse Threadx Usbx. Its CVSS base score is 6.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

components include components in host class, related to CDC ACM 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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1489 Service Stop Impact
Adversaries may stop or disable services on a system to render those services unavailable to legitimate users.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-48698Same product: Eclipse Threadx Usbx
CVE-2023-48697Same product: Eclipse Threadx Usbx
CVE-2023-48694Same product: Eclipse Threadx Usbx
CVE-2025-55096Same product: Eclipse Threadx Usbx
CVE-2025-55095Same product: Eclipse Threadx Usbx
CVE-2025-55099Same product: Eclipse Threadx Usbx
CVE-2025-55098Same product: Eclipse Threadx Usbx
CVE-2025-55097Same product: Eclipse Threadx Usbx
CVE-2025-55100Same product: Eclipse Threadx Usbx
CVE-2023-48695Same product: Eclipse Threadx Usbx

Affected Assets

eclipse
threadx usbx
≤ 6.3.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-754

Requires detection and response to audit logging failures as an unusual or exceptional condition.

addresses: CWE-754

Implements detection of unusual or exceptional conditions followed by safe mode entry, reducing the window for exploitation of unchecked conditions.

addresses: CWE-754

Training ensures users perform required checks for unusual or exceptional conditions as part of contingency roles, limiting attacker leverage from skipped validations.

addresses: CWE-754

IR testing directly validates checks for unusual or exceptional conditions that could indicate security incidents.

addresses: CWE-754

Requires ongoing monitoring of organization-defined metrics and analysis, enabling checks for unusual or exceptional conditions.

addresses: CWE-754

Security testing routinely checks for unusual or exceptional inputs/conditions, identifying missing validation steps that flaw remediation then resolves.

addresses: CWE-754

Requires detection of unusual conditions followed by a controlled transition to the defined failure state.

addresses: CWE-754

MTTF determination forces explicit checks for conditions that precede predictable component failure.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly require proper checks and handling for exceptional conditions throughout the SDLC.

DE.CM-09 partial match
prevents

Runtime monitoring of software and environments can detect adverse events triggered by unhandled exceptional conditions.

ID.AM-08 partial match
prevents

Lifecycle management includes secure development and maintenance phases that reduce memory-safety defects.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free flaws via scanning or analysis.

PR.PS-02 partial match
prevents

Routine patching and replacement can eliminate known instances of expired-pointer bugs.

PR.PS-04 partial match
prevents

Generating logs of exceptions and errors enables detection of improper handling of unusual conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance verifies handling of error and exceptional conditions.

A.8.15 Logging partial match
finds

Logging can record unhandled exceptions but does not prevent the weakness itself.

finds

Monitoring may detect symptoms of unhandled conditions but does not eliminate the root weakness.

prevents

Secure development life cycle mandates exception handling and input validation that directly prevent missing checks for unusual conditions.

prevents

Application security requirements explicitly call for handling of exceptional conditions and error paths.

prevents

Secure system architecture and engineering principles require robust error and exception handling mechanisms.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-754
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-754
Oracle Linux 9 (1 rule)
  • V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-754

References