# CVE-2022-29246: Potential buffer overflow in function DFU upload in Azure RTOS USBX

> A buffer overflow in Azure RTOS USBX DFU upload allows attackers to execute arbitrary code or bypass security features via crafted control requests.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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-hh5p-x584-j8hv

## What is CVE-2022-29246?

CVE-2022-29246 is a critical 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. Prior to version 6.1.11, he USBX DFU UPLOAD functionality may be utilized to introduce a buffer overflow resulting in overwrite of memory contents. In particular cases this may allow an attacker to bypass security features or execute arbitrary code. The implementation of `ux_device_class_dfu_control_request` function does not assure that a buffer overflow will not occur during handling of the DFU UPLOAD command. When an attacker issues the `UX_SLAVE_CLASS_DFU_COMMAND_UPLOAD` control transfer request with `wLenght` larger than the buffer size (`UX_SLAVE_REQUEST_CONTROL_MAX_LENGTH`, 256 bytes), depending on the actual implementation of `dfu -> ux_slave_class_dfu_read`, a buffer overflow may occur. In example `ux_slave_class_dfu_read` may read 4096 bytes (or more up to 65k) to a 256 byte buffer ultimately resulting in an overflow. Furthermore in case an attacker has some control over the read flash memory, this may result in execution of arbitrary code and platform compromise. A fix for this issue has been included in USBX release 6.1.11. As a workaround, align request and buffer size to assure that buffer boundaries are respected.

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

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

It affects 1 product.


Products: Eclipse Threadx Usbx.

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

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

## Is CVE-2022-29246 being exploited?

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

## Other vulnerabilities in azure-rtos usbx

- [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-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-29246 and fix it if it is affected.

What it is: CVE-2022-29246 is a critical 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-29246 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-29246/ (Markdown: https://insights.sbomify.com/CVE-2022-29246/index.md)
```

## Sources

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

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