# CVE-2023-35121: Privilege escalation in Intel(R) oneAPI DPC++/C++ Compiler software

> An authenticated local user can escalate privileges due to improper access control in the Intel oneAPI DPC++/C++ Compiler.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** No
- **Published:** 14 Feb 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vpq8-9rj2-88fw

## What is CVE-2023-35121?

CVE-2023-35121 is a high-severity vulnerability in Intel(R) oneAPI DPC++/C++ Compiler software, published on 14 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control in the Intel(R) oneAPI DPC++/C++ Compiler before version 2022.2.1 for some Intel(R) oneAPI Toolkits before version  2022.3.1 may allow authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-284 (Improper Access Control)

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

It affects 16 products.


Products: Intel Advisor, Intel Cluster Checker, Intel Distribution for Python, Intel Inspector, Intel Integrated Performance Primitives, Intel Integrated Performance Primitives Cryptography, Intel Mpi Library, Intel Oneapi Ai Analytics Toolkit, Intel Oneapi Base Toolkit, Intel Oneapi Deep Neural Network, Intel Oneapi Hpc Toolkit, Intel Oneapi Iot Toolkit, Intel Oneapi Math Kernel Library, Intel Threading Building Blocks, Intel Trace Analyzer and Collector, Intel Vtune Profiler.

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

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

## Is CVE-2023-35121 being exploited?

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

## Other vulnerabilities in Intel(R) oneAPI DPC++/C++ Compiler software

- [CVE-2022-21128](https://insights.sbomify.com/CVE-2022-21128/): Privilege escalation in Intel(R) Advisor software (high 7.8)
- [CVE-2021-23152](https://insights.sbomify.com/CVE-2021-23152/): Privilege escalation in Intel(R) Advisor software (high 7.8)
- [CVE-2021-33129](https://insights.sbomify.com/CVE-2021-33129/): Privilege escalation in Intel(R) Advisor (high 7.8)
- [CVE-2023-24592](https://insights.sbomify.com/CVE-2023-24592/): Path traversal in Intel(R) oneAPI Toolkits and Component software (high 7.3)
- [CVE-2017-5682](https://insights.sbomify.com/CVE-2017-5682/): Privilege escalation in Intel Parallel Studio XE, Intel System Studio, Intel VTune Amplifier, Intel Inspector, Intel Advisor, Intel MPI Library, Intel Trace Analyzer and Collector, Intel Integrated Performance Primitives, Cryptography for Intel Integrated Performance Primitives, Intel Math Kernel Library, Intel Data Analytics Acceleration Library, Intel Threading Building Blocks Before 2017 Update 2 (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-35121 is a high-severity vulnerability in Intel(R) oneAPI DPC++/C++ Compiler software, published on 14 Feb 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-35121 in the wild and no public exploit code.

Affected product: Intel(R) oneAPI DPC++/C++ Compiler software. 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-35121/ (Markdown: https://insights.sbomify.com/CVE-2023-35121/index.md)
```

## Sources

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

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