dbcve.org
AdvisorApplication · Intel

CVE-2023-35121

HIGH · 7.8 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 2021.8 / 2021.10 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
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.

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

Intel oneAPI DPC++/C++ Compiler before version 2022.2.1 contains an improper access control vulnerability that allows an authenticated local user to potentially escalate privileges. This is a compiler/toolchain vulnerability where the access control mechanism fails to properly restrict operations, enabling a local attacker with valid credentials to gain elevated system access.

MitigationUpgrade Intel oneAPI DPC++/C++ Compiler to version 2022.2.1 or later, and Intel oneAPI Toolkits to version 2023.3.1 or later. Verify that existing projects compile and function correctly after the upgrade.

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
AdvisorApplication
Affected:< 2023.2
Cluster CheckerApplication
Affected:= 2021.7.3
Distribution For PythonApplication
Affected:= 2023.1
InspectorApplication
Affected:< 2023.2
Integrated Performance PrimitivesApplication
Affected:= 2021.9
Integrated Performance Primitives CryptographyApplication
Affected:< 2021.8
Mpi LibraryApplication
Affected:< 2021.10
Oneapi Ai Analytics ToolkitApplication
Affected:= 2023.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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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. Identify Intel oneAPI DPC++/C++ Compiler installation
    Run 'dpcpp --version' or 'icpx --version' from command line. If those commands are not found, search for the compiler in typical installation directories such as /opt/intel/oneapi/ or C:\Program Files\Intel\oneAPI\
    Affected if The compiler version exists and is earlier than 2022.2.1, or the compiler is not found but other Intel oneAPI components are present with known vulnerable versions
  2. Check Intel Advisor version
    Run 'advisor --version' or inspect the installation directory for version information
    Affected if Version is installed and lower than 2023.2
  3. Check Intel Inspector version
    Run 'inspxe-cl --version' or inspect the installation directory for version information
    Affected if Version is installed and lower than 2023.2
  4. Check Intel MPI Library version
    Run 'mpivars.bat' or 'mpivars.sh' with version flag, or check the installation directory
    Affected if Version is installed and lower than 2021.10
  5. Verify access control on compiler directories
    On Linux, inspect permissions on /opt/intel/oneapi/compiler directory using 'ls -la'. On Windows, right-click the installation folder and check Properties > Security to confirm if standard users have write or execute permissions beyond their normal scope
    Affected if Non-privileged users have elevated permissions on compiler installation directories or can modify compiler components
  6. Check for other affected Intel tools
    Query installed Intel oneAPI components using 'oneapi-cli' or by listing contents of the Intel oneAPI installation directory. Look specifically for: Cluster Checker 2021.7.3, Distribution for Python 2023.1, IPP 2021.9, IPP Cryptography < 2021.8, and AI Analytics Toolkit 2023.2
    Affected if Any of these specific versions are installed alongside the vulnerable compiler

Your environment is affected if Intel oneAPI DPC++/C++ Compiler version is earlier than 2022.2.1, or if any of the listed vulnerable Intel tool versions are installed, and local users have access to the system where these components are running.

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 2021.8 / 2021.10 / 2023.2 or later
Fixed in 2021.82021.102023.2
Interim mitigation

Upgrade Intel oneAPI DPC++/C++ Compiler to version 2022.2.1 or later, and Intel oneAPI Toolkits to version 2023.3.1 or later. Verify that existing projects compile and function correctly after the upgrade.

Recommended fix Moderate confidence

2022.3.1 for oneAPI Toolkits; 2022.2.1 for DPC++/C++ Compiler; 2023.2 for Advisor and Inspector; 2021.10 for MPI Library; 2021.8 for IPP Cryptography

  1. 1. Identify all Intel oneAPI components installed using the Intel® oneAPI Installer or system package manager
  2. 2. For Intel Advisor: upgrade to version 2023.2 or later
  3. 3. For Intel Inspector: upgrade to version 2023.2 or later
  4. 4. For Intel Integrated Performance Primitives Cryptography: upgrade to version 2021.8 or later
  5. 5. For Intel MPI Library: upgrade to version 2021.10 or later
  6. 6. For Intel DPC++/C++ Compiler: upgrade to version 2022.2.1 or later
  7. 7. For Intel oneAPI Toolkits: ensure the toolkit version is 2022.3.1 or later
  8. 8. Verify the fixes by checking the installed component versions after upgrade
Caveat Upgrading oneAPI components may require recompiling applications and updating project configurations; ensure compatibility with dependent software before upgrading

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

Fix this in Advisor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,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 $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35121 — 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-35121 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