# CVE-2023-43490: Information disclosure in Intel(R) Xeon(R) D Processors with Intel(R) SGX

> A privileged local attacker can exploit incorrect microcode keying calculations in Intel Xeon D processors with SGX to disclose sensitive information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:N/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:** Yes
- **Published:** 14 Mar 2024
- **Updated:** 13 Feb 2025
- **Also known as:** ALPINE-CVE-2023-43490, BELL-CVE-2023-43490, DEBIAN-CVE-2023-43490, GHSA-vww6-323c-pxr2, UBUNTU-CVE-2023-43490

## What is CVE-2023-43490?

CVE-2023-43490 is a medium-severity vulnerability in Intel(R) Xeon(R) D Processors with Intel(R) SGX, 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

Incorrect calculation in microcode keying mechanism for some Intel(R) Xeon(R) D Processors with Intel(R) SGX may allow a privileged user to potentially enable information disclosure via local access.

Weakness: CWE-682 (Incorrect Calculation)

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


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

Apply the vendor's patch.

## Is CVE-2023-43490 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43490 is a medium-severity vulnerability in Intel(R) Xeon(R) D Processors with Intel(R) SGX, 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-43490 in the wild and no public exploit code.

Affected product: Intel(R) Xeon(R) D Processors with Intel(R) SGX. 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-43490/ (Markdown: https://insights.sbomify.com/CVE-2023-43490/index.md)
```

## Sources

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

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