# CVE-2023-32666: Privilege escalation in 4th Generation Intel(R) Xeon(R) Processors when using Intel(R) SGX or Intel(R) TDX

> A privileged local attacker can escalate privileges via improper access control in the debug interface of Intel Xeon processors using SGX or TDX.

- **Severity:** High 7.2 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-9hpm-6w4c-hxh2

## What is CVE-2023-32666?

CVE-2023-32666 is a high-severity vulnerability in 4th Generation Intel(R) Xeon(R) Processors when using Intel(R) SGX or Intel(R) TDX, published on 14 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On-chip debug and test interface with improper access control in some 4th Generation Intel(R) Xeon(R) Processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.

Weakness: CWE-1191 (On-Chip Debug and Test Interface With Improper Access Control)

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


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

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

## Is CVE-2023-32666 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32666 is a high-severity vulnerability in 4th Generation Intel(R) Xeon(R) Processors when using Intel(R) SGX or Intel(R) TDX, published on 14 Mar 2024. 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-32666 in the wild and no public exploit code.

Affected product: 4th Generation Intel(R) Xeon(R) Processors when using Intel(R) SGX or Intel(R) TDX. 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-32666/ (Markdown: https://insights.sbomify.com/CVE-2023-32666/index.md)
```

## Sources

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

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