dbcve.org
Oneapi Dpc\+\+\/c\+\+ CompilerApplication · Intel

CVE-2022-38136

HIGH · 7.3 CVSS v3.1 Published 2023-02-06
Fix available
A fix is available. Upgrade to 2022.2.1 or later.
See remediation →
73/100
Remediation priority · Elevated

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 the Intel(R) oneAPI DPC++/C++ Compiler for Windows and Intel Fortran Compiler for Windows before version 2022.2.1 for some Intel(R) oneAPI Toolkits before version 2022.3.1 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

The Intel oneAPI DPC++/C++ Compiler and Fortran Compiler for Windows load dynamic-link libraries (DLLs) from an uncontrolled search path, allowing an authenticated local attacker to place malicious DLLs in locations where the compiler searches for dependencies. When the compiler loads these DLLs, it executes them with elevated privileges, achieving local privilege escalation.

MitigationUpgrade Intel oneAPI DPC++/C++ Compiler and Fortran Compiler to version 2022.2.1 or later, or Intel oneAPI Toolkits to version 2022.3.1 or later. Alternatively, ensure the compiler's execution path does not include user-writable directories.

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
Oneapi Dpc\+\+\/c\+\+ CompilerApplication
Affected:< 2022.2.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 DPC++/C++ Compiler installation
    Search for dpcpp.exe in typical installation directories such as C:\Program Files (x86)\Intel\oneAPI\ or C:\Program Files\Intel\oneAPI\, or use 'where dpcpp' from an elevated command prompt
    Affected if dpcpp.exe is not found in any standard Intel oneAPI installation path
  2. Identify installed compiler version
    Run 'dpcpp.exe --version' or right-click the dpcpp.exe file, select Properties, and check the Version tab for the product version
    Affected if The version displayed is lower than 2022.2.1 or the version field cannot be determined
  3. Verify compiler execution path
    Check the PATH environment variable and the working directory from which the compiler is typically invoked. Look for user-writable locations such as temp folders, project directories, or network shares included in PATH before the Intel installation directory
    Affected if User-writable directories appear earlier in PATH than the Intel oneAPI compiler directory, or the compiler is invoked from a user-writable working directory

You are affected if Intel oneAPI DPC++/C++ Compiler version is installed and the version is below 2022.2.1, or if user-writable directories are present in the search path before the compiler's installation directory.

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 2022.2.1 or later
Fixed in 2022.2.1
Interim mitigation

Upgrade Intel oneAPI DPC++/C++ Compiler and Fortran Compiler to version 2022.2.1 or later, or Intel oneAPI Toolkits to version 2022.3.1 or later. Alternatively, ensure the compiler's execution path does not include user-writable directories.

Recommended fix High confidence

Intel oneAPI DPC++/C++ Compiler 2022.2.1 or later; Intel Fortran Compiler 2022.2.1 or later; Intel oneAPI Toolkits 2022.3.1 or later

  1. Identify the currently installed version of Intel(R) oneAPI DPC++/C++ Compiler for Windows by checking the installed programs list or running 'icx --version'
  2. Identify the currently installed version of Intel Fortran Compiler for Windows if applicable
  3. Download Intel oneAPI Toolkit version 2022.2.1 or later from the official Intel download page at www.intel.com
  4. Run the Intel oneAPI installer and follow the on-screen prompts to upgrade the DPC++/C++ Compiler to version 2022.2.1 or later
  5. If Intel Fortran Compiler is also installed, ensure it is also upgraded to version 2022.2.1 or later
  6. Restart any development environments and verify the new compiler version using 'icx --version'
  7. Confirm the DLL search path is now properly controlled and no unauthorized DLL locations are in the system PATH

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

Fix this in Oneapi Dpc\+\+\/c\+\+ Compiler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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