dbcve.org
C\+\+ CompilerApplication · Intel

CVE-2022-41342

HIGH · 7.8 CVSS v3.1 Published 2023-02-06
Fix available
A fix is available. Upgrade to 2021.7.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 buffer restrictions in the Intel(R) C++ Compiler Classic before version 2021.7.1 for some Intel(R) oneAPI Toolkits before version 2022.3.1 may allow a privileged 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 buffer restrictions in Intel C++ Compiler Classic allow a privileged local user to potentially escalate privileges. The vulnerability stems from inadequate bounds checking in the compiler's buffer handling, which a local attacker with existing privileged access could exploit to gain higher-level system privileges.

MitigationUpgrade Intel C++ Compiler Classic to version 2021.7.1 or later, or Intel oneAPI Toolkits to version 2022.3.1 or later, to remediate the buffer restriction 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
C\+\+ CompilerApplication
Affected:< 2021.7.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. Determine if Intel C++ Compiler Classic is installed
    Look for Intel C++ Compiler components in the system. Common locations include program files directories or Intel installation folders. Use system inventory or package management tools to identify if the compiler is present.
    Affected if Intel C++ Compiler Classic is found on the system
  2. Identify the installed Intel C++ Compiler version
    Run the compiler with version information flags (such as --version or -V) or check the compiler's About/Diagnostics information. Alternatively, inspect the compiler binary properties or installation metadata.
    Affected if The version number returned is below 2021.7.1
  3. Verify compiler is running with elevated privileges
    Since this is a local privilege escalation, confirm whether the compiler or build processes execute with elevated or privileged system access.
    Affected if The compiler or associated build processes run with privileged access

A system is affected if Intel C++ Compiler Classic is installed with a version lower than 2021.7.1 and the compiler or its build workflows execute with elevated system 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 2021.7.1 or later
Fixed in 2021.7.1
Interim mitigation

Upgrade Intel C++ Compiler Classic to version 2021.7.1 or later, or Intel oneAPI Toolkits to version 2022.3.1 or later, to remediate the buffer restriction vulnerability.

Recommended fix High confidence

Intel C++ Compiler Classic 2021.7.1 or later / oneAPI Toolkit 2022.3.1 or later

  1. 1. Identify the current version of Intel(R) C++ Compiler Classic installed in your environment
  2. 2. Download Intel(R) C++ Compiler Classic version 2021.7.1 or later from the Intel website or your Intel oneAPI distribution
  3. 3. Install the updated compiler version following Intel's standard installation procedures
  4. 4. Verify the new version is correctly installed by running `icpc --version` or checking the compiler documentation
  5. 5. Rebuild any projects that were compiled with the affected compiler version to ensure they benefit from the security fix
  6. 6. Test the rebuilt applications to confirm functionality remains intact

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

Fix this in C\+\+ Compiler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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