# CVE-2022-29223: Buffer overflow on HUB descriptor in Azure RTOS USBX

> An attacker can trigger a buffer overflow in Azure RTOS USBX by providing a malicious HUB descriptor, potentially leading to code execution or denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-2qc5-385m-x862

## What is CVE-2022-29223?

CVE-2022-29223 is a high-severity memory corruption vulnerability in azure-rtos usbx, published on 24 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack. In versions prior to 6.1.10, an attacker can cause a buffer overflow by providing the Azure RTOS USBX host stack a HUB descriptor with `bNbPorts` set to a value greater than `UX_MAX_TT` which defaults to 8. For a `bNbPorts` value of 255, the implementation of `ux_host_class_hub_descriptor_get` function will modify the contents of `hub` -> `ux_host_class_hub_device` -> `ux_device_hub_tt` array violating the end boundary by 255 - `UX_MAX_TT` items. The USB host stack needs to validate the number of ports reported by the hub, and if the value is larger than UX_MAX_TT, USB stack needs to reject the request. This fix has been included in USBX release 6.1.10.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-29223?

It affects 1 product.


Products: Eclipse Threadx Usbx.

## How do I fix CVE-2022-29223?

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

## Is CVE-2022-29223 being exploited?

There is no known exploitation of CVE-2022-29223 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-2023-48695](https://insights.sbomify.com/CVE-2023-48695/): Azure RTOS USBX Remote Code Execution Vulnerability (high 7.2)
- [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-2022-29223 and fix it if it is affected.

What it is: CVE-2022-29223 is a high-severity memory corruption vulnerability in azure-rtos usbx, published on 24 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29223 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-2022-29223/ (Markdown: https://insights.sbomify.com/CVE-2022-29223/index.md)
```

## Sources

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

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