# CVE-2023-32618: Privilege escalation in Intel(R) oneAPI Toolkit and component software installers

> An authenticated local attacker can escalate privileges via an uncontrolled search path in Intel oneAPI Toolkit installers.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Feb 2024
- **Updated:** 7 Aug 2024

## What is CVE-2023-32618?

CVE-2023-32618 is a medium-severity vulnerability in Intel(R) oneAPI Toolkit and component software installers, published on 14 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Uncontrolled search path in some Intel(R) oneAPI Toolkit and component software installers before version 4.3.2 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Intel Oneapi.

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

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

## Is CVE-2023-32618 being exploited?

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

## Other vulnerabilities in Intel(R) oneAPI Toolkit and component software installers

- [CVE-2023-28715](https://insights.sbomify.com/CVE-2023-28715/): Missing authorization in Intel(R) oneAPI Toolkit and component software installers (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32618 is a medium-severity vulnerability in Intel(R) oneAPI Toolkit and component software installers, published on 14 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-32618 in the wild and no public exploit code.

Affected product: Intel(R) oneAPI Toolkit and component software installers. 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-32618/ (Markdown: https://insights.sbomify.com/CVE-2023-32618/index.md)
```

## Sources

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

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