# CVE-2023-48693: Azure RTOS ThreadX Remote Code Execution Vulnerability


- **Severity:** High 8.7 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-p7w6-62rq-vrf9

## What is CVE-2023-48693?

CVE-2023-48693 is a high-severity vulnerability in azure-rtos threadx, published on 5 Dec 2023. 

### Official description

Azure RTOS ThreadX is an advanced real-time operating system (RTOS) designed specifically for deeply embedded applications. An attacker can cause arbitrary read and write due to vulnerability in parameter checking mechanism in Azure RTOS ThreadX, which may lead to privilege escalation. The affected components include RTOS ThreadX v6.2.1 and below. The fixes have been included in ThreadX release 6.3.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Microsoft Azure Rtos Threadx.

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

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

## Is CVE-2023-48693 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-48693 is a high-severity vulnerability in azure-rtos threadx, published on 5 Dec 2023. 
Exploitation: There is no known exploitation of CVE-2023-48693 in the wild and no public exploit code.

Affected product: azure-rtos threadx. 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-48693/ (Markdown: https://insights.sbomify.com/CVE-2023-48693/index.md)
```

## Sources

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

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