# CVE-2023-48695: Azure RTOS USBX Remote Code Execution Vulnerability

> An attacker can achieve remote code execution via out-of-bounds write vulnerabilities in the Azure RTOS USBX stack.

- **Severity:** High 7.2 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2023
- **Updated:** 29 May 2025
- **Also known as:** GHSA-mwj9-rpph-v8wc

## What is CVE-2023-48695?

CVE-2023-48695 is a high-severity memory corruption vulnerability in azure-rtos usbx, published on 5 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-48695?

It affects 1 product.


Products: Eclipse Threadx Usbx.

## How do I fix CVE-2023-48695?

No fix has been published for CVE-2023-48695 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-48695 being exploited?

There is no known exploitation of CVE-2023-48695 in the wild and no public exploit code.

## Other vulnerabilities in azure-rtos usbx

- [CVE-2022-29246](https://insights.sbomify.com/CVE-2022-29246/): Potential buffer overflow in function DFU upload in Azure RTOS USBX (critical 9.8)
- [CVE-2022-39293](https://insights.sbomify.com/CVE-2022-39293/): Azure RTOS USBX Host PIMA vulnerable to read integer underflow with buffer overflow (high 8.6)
- [CVE-2022-36063](https://insights.sbomify.com/CVE-2022-36063/): USBX Host CDC ECM integer underflow with buffer overflow (high 7.6)
- [CVE-2022-29223](https://insights.sbomify.com/CVE-2022-29223/): Buffer overflow on HUB descriptor in Azure RTOS USBX (high 7.5)
- [CVE-2023-48694](https://insights.sbomify.com/CVE-2023-48694/): Azure RTOS USBX Remote Code Execution Vulnerability (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48695 and fix it if it is affected.

What it is: CVE-2023-48695 is a high-severity memory corruption vulnerability in azure-rtos usbx, published on 5 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-48695 in the wild and no public exploit code.

Affected product: azure-rtos usbx. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-48695/ (Markdown: https://insights.sbomify.com/CVE-2023-48695/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-48695
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-48695
- OSV: https://osv.dev/vulnerability/CVE-2023-48695

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-48695/
Summaries are generated and may contain mistakes; the official description above is the record.