# CVE-2022-39344: Azure RTOS USBX vulnerable to buffer overflow

> A buffer overflow in Azure RTOS USBX allows attackers to execute arbitrary code or bypass security features via USB DFU UPLOAD commands.

- **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:** 4 Nov 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-m9p8-xrp7-vvqp

## What is CVE-2022-39344?

CVE-2022-39344 is a critical memory corruption vulnerability in azure-rtos usbx, published on 4 Nov 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, that is fully integrated with Azure RTOS ThreadX. Prior to version 6.1.12, the USB 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 prevents buffer overflow during handling of DFU UPLOAD command when current state is `UX_SYSTEM_DFU_STATE_DFU_IDLE`. This issue has been patched, please upgrade to version 6.1.12. As a workaround, add the `UPLOAD_LENGTH` check in all possible states.

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

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

It affects 1 product.


Products: Microsoft Azure Rtos Usbx.

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

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

## Is CVE-2022-39344 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39344 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39344 and fix it if it is affected.

What it is: CVE-2022-39344 is a critical memory corruption vulnerability in azure-rtos usbx, published on 4 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39344 exists.

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-39344/ (Markdown: https://insights.sbomify.com/CVE-2022-39344/index.md)
```

## Sources

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

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