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

CVE-2022-40196

HIGH · 7.8 CVSS v3.1 Published 2023-02-06
Fix available
A fix is available. Upgrade to 2022.2.1 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 and Intel C++ Compiler Classic before version 2021.7.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 · moderate confidence

Improper access control in Intel's DPC++/C++ Compiler and Intel C++ Compiler Classic allows an authenticated local user to potentially escalate privileges. This is a local privilege escalation vulnerability affecting specific versions of Intel compilers used in oneAPI Toolkits.

MitigationUpgrade Intel(R) oneAPI DPC++/C++ Compiler to version 2022.2.1 or later, Intel C++ Compiler Classic to version 2021.7.1 or later, and Intel oneAPI Toolkits to version 2022.3.1 or later.

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
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 DPC++/C++ Compiler installation
    Search for the dpcpp compiler executable in common Intel oneAPI installation paths such as /opt/intel/oneapi/ or C:\Program Files\Intel\oneapi\, or check if the dpcpp command is available in PATH
    Affected if The compiler is not found in expected locations and dpcpp command is not available in PATH, indicating the product may not be installed
  2. Identify installed DPC++ compiler version
    Run 'dpcpp --version' or 'dpcpp -v' from command line to display the compiler version information
    Affected if The command executes and returns a version number that can be compared against the affected range
  3. Compare version against affected range
    Interpret the version output and compare numerically to 2022.2.1 - note that versions below 2022.2.1 (such as 2022.2.0, 2022.1.x, 2021.x series) are within the affected range
    Affected if Installed version is less than 2022.2.1 (for example 2022.2.0, 2022.1.0, 2021.4.0, etc.)
  4. Verify if Intel C++ Compiler Classic is present
    Check for the presence of the 'icc' compiler executable in Intel oneAPI paths or PATH, run 'icc --version' to confirm installation and version
    Affected if Intel C++ Compiler Classic is installed and running a version prior to 2021.7.1

Your environment is affected if Intel oneAPI DPC++/C++ Compiler version is below 2022.2.1 or Intel C++ Compiler Classic version is below 2021.7.1, and either compiler is installed and accessible to local users.

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(R) oneAPI DPC++/C++ Compiler to version 2022.2.1 or later, Intel C++ Compiler Classic to version 2021.7.1 or later, and Intel oneAPI Toolkits to version 2022.3.1 or later.

Recommended fix High confidence

Intel oneAPI DPC++/C++ Compiler 2022.2.1 or later; Intel C++ Compiler Classic 2021.7.1 or later (for oneAPI Toolkits: 2022.3.1 or later)

  1. 1. Identify the currently installed Intel oneAPI DPC++/C++ Compiler version using 'sycl-ls' or checking the installation directory
  2. 2. Identify the currently installed Intel C++ Compiler Classic version using 'icpc --version'
  3. 3. Download Intel oneAPI DPC++/C++ Compiler version 2022.2.1 or later from the official Intel website or repository
  4. 4. Download Intel C++ Compiler Classic version 2021.7.1 or later (or oneAPI Toolkit version 2022.3.1 or later for bundled components)
  5. 5. Run the Intel installer and follow the on-screen prompts to update the compiler(s)
  6. 6. Verify the installation by running 'icpc --version' and/or 'sycl-ls' to confirm the updated version is active
  7. 7. Rebuild any projects that use the compiler to ensure compatibility with the updated version

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

Fix this in Oneapi Dpc\+\+\/c\+\+ Compiler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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