dbcve.org
AdvisorApplication · Intel

CVE-2023-29162

MEDIUM · 6.0 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 2021.8 / 2021.10 or later.
See remediation →
62/100
Remediation priority · Elevated
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 the Intel(R) C++ Compiler Classic before version 2021.8 for 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

Intel C++ Compiler Classic contains an improper buffer restriction vulnerability that could allow a privileged local user to potentially escalate privileges. The flaw exists in versions prior to 2021.8 for Intel oneAPI Toolkits prior to version 2022.3.1.

MitigationUpdate Intel C++ Compiler Classic to version 2021.8 or later (for oneAPI Toolkits, update to 2022.3.1 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
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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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

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 C++ Compiler Classic installation
    Locate the Intel C++ Compiler Classic binaries or installation directory. On Windows, check C:\Program Files\Intel\oneAPI\ or C:\Program Files (x86)\Intel\oneAPI\. On Linux, check /opt/intel/oneapi/ or /usr/local/oneapi/. Look for folders named 'compiler' or 'icx' or 'icl'.
    Affected if Intel C++ Compiler Classic is present on the system
  2. Check Intel C++ Compiler Classic version
    Run 'icx --version' or 'icl --version' from the compiler bin directory, or check the version info of the compiler executable. Alternatively, inspect the compiler's release notes or version file in the installation directory.
    Affected if The version is earlier than 2021.8 (or the version cannot be determined and the compiler is present)
  3. Check Intel oneAPI Toolkit version if applicable
    If Intel C++ Compiler Classic is bundled with a oneAPI Toolkit, check the toolkit version by running 'oneapi--version' or inspecting the oneAPI installation metadata. On Windows, check Add/Remove Programs for Intel oneAPI Toolkit version. On Linux, check the oneAPI installation metadata in /opt/intel/oneapi/.
    Affected if oneAPI Toolkit version is earlier than 2022.3.1 when bundled with the compiler
  4. Verify affected Intel component products
    If Intel C++ Compiler Classic is not directly installed, check for the presence of any affected products: Intel Advisor (< 2023.2), Intel Cluster Checker (= 2021.7.3), Intel Distribution for Python (= 2023.1), Intel Inspector (< 2023.2), Intel Integrated Performance Primitives (= 2021.9), Intel IPP Cryptography (< 2021.8), Intel MPI Library (< 2021.10), or Intel oneAPI AI Analytics Toolkit (= 2023.2). Check via installed programs list or product-specific version commands.
    Affected if Any of these specific product versions are installed on the system

The system is affected if Intel C++ Compiler Classic version is prior to 2021.8 or oneAPI Toolkit is prior to 2022.3.1, OR if any listed affected Intel product versions are present, as they bundle the vulnerable compiler component.

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

Update Intel C++ Compiler Classic to version 2021.8 or later (for oneAPI Toolkits, update to 2022.3.1 or later) to remediate this vulnerability.

Recommended fix High confidence

Intel C++ Compiler Classic 2021.8 or later / oneAPI Toolkits 2022.3.1 or later

  1. 1. Identify the specific Intel software product(s) from the affected list that are installed (Advisor, Cluster Checker, Distribution For Python, Inspector, Integrated Performance Primitives, Integrated Performance Primitives Cryptography, Mpi Library, or Oneapi Ai Analytics Toolkit)
  2. 2. For each affected product, check the current installed version
  3. 3. Download and install the patched version from Intel's official download portal or through your Intel oneAPI installation mechanism
  4. 4. For Intel C++ Compiler Classic: upgrade to version 2021.8 or later
  5. 5. For Intel oneAPI Toolkits: upgrade to version 2022.3.1 or later
  6. 6. Verify the installed version matches the fixed release after installation
  7. 7. Restart any running services or applications that use the affected components
Caveat Ensure compatibility with existing build systems and project configurations as minor version upgrades may introduce subtle compiler behavior changes

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

Fix this in Advisor 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-2023-29162 — 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-29162 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