# CVE-2023-45733: Race condition in Intel(R) Processors

> An authenticated local attacker can exploit hardware race conditions in Intel processors to achieve partial information disclosure.

- **Severity:** Low 2.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** ALPINE-CVE-2023-45733, BELL-CVE-2023-45733, DEBIAN-CVE-2023-45733, GHSA-fg3p-42cv-c5cm, UBUNTU-CVE-2023-45733

## What is CVE-2023-45733?

CVE-2023-45733 is a low-severity vulnerability in Intel(R) Processors, published on 16 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hardware logic contains race conditions in some Intel(R) Processors may allow an authenticated user to potentially enable partial information disclosure via local access.

Weakness: CWE-1298 (Hardware Logic Contains Race Conditions)

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


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

Apply the vendor's patch.

## Is CVE-2023-45733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45733 is a low-severity vulnerability in Intel(R) Processors, published on 16 May 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-45733 in the wild and no public exploit code.

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

## Sources

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

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