dbcve.org
OneapiApplication · Intel

CVE-2023-32618

HIGH · 7.8 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 4.3.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Uncontrolled search path vulnerability in Intel oneAPI Toolkit and component software installers before version 4.3.2 allows an authenticated local user to potentially place malicious files in the search path used during installation, leading to privilege escalation when the installer executes with elevated privileges.

MitigationUpgrade Intel oneAPI Toolkit and component software to version 4.3.2 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OneapiApplication
Affected:< 4.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Intel oneAPI Toolkit installation
    Check for Intel oneAPI Toolkit in standard installation directories: C:\Program Files\Intel\oneAPI (Windows) or /opt/intel/oneapi (Linux). Also check the Windows Registry under HKLM\SOFTWARE\Intel\OneAPI for installation records.
    Affected if Intel oneAPI Toolkit is found installed on the system
  2. Identify installed Intel oneAPI version
    On Windows, check the version property of the installer executable or review the Intel OneAPI metadata in the installation directory. On Linux, run 'intel-oneapi--version' or check the version file in the installation directory if available.
    Affected if The installed version number cannot be determined or is below 4.3.2
  3. Verify installer components for search path vulnerability
    Review the installer configuration or manifest files for any custom search paths defined during installation. Check if the installer allows user-controlled paths in its configuration.
    Affected if Custom or user-influenced search paths are defined in the installer configuration that could be exploited
  4. Check for prior installation sessions with elevated privileges
    Review installation logs or temporary directories used during Intel oneAPI installations. Look for evidence of installer executions with elevated privileges (check Windows Event Viewer for MSI installer events with System or Administrator context).
    Affected if Historical installation events show the installer has been run with elevated privileges on this system

A system is affected if Intel oneAPI Toolkit or its component software is installed with a version lower than 4.3.2, and the installer has been or could be run with elevated privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.3.2 or later
Fixed in 4.3.2
Interim mitigation

Upgrade Intel oneAPI Toolkit and component software to version 4.3.2 or later to remediate this vulnerability.

Recommended fix High confidence

Intel oneAPI Toolkit 4.3.2 or later

  1. 1. Check the currently installed Intel oneAPI Toolkit version via the system control panel or by running 'oneapi-cli --version' if available
  2. 2. Navigate to the official Intel oneAPI Toolkit download page at www.intel.com
  3. 3. Download Intel oneAPI Toolkit version 4.3.2 or the latest available version
  4. 4. Uninstall the current vulnerable version using the Windows Add/Remove Programs feature or the Intel uninstaller
  5. 5. Run the downloaded installer for version 4.3.2 or later as an administrator
  6. 6. Follow the installation wizard prompts to complete the installation
  7. 7. Verify the installed version is 4.3.2 or later after installation completes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Oneapi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32618 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32618 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data