dbcve.org
Oneapi Hpc ToolkitApplication · Intel

CVE-2023-23910

HIGH · 7.8 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 2021.8.0 / 2023.0.0 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
Out-of-bounds write for some Intel(R) Trace Analyzer and Collector software before version 2021.8.0 published Dec 2022 may allow an authenticated user to potentially 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

An out-of-bounds write vulnerability exists in Intel Trace Analyzer and Collector software versions prior to 2021.8.0. The flaw allows an authenticated local user to potentially escalate privileges through memory corruption. This is a memory safety vulnerability in a specialized performance analysis tool used for analyzing MPI communications and trace data.

MitigationUpgrade Intel Trace Analyzer and Collector to version 2021.8.0 or later. Verify the upgrade in a test environment before production deployment due to the specialized nature of the software.

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 Hpc ToolkitApplication
Affected:< 2023.0.0
Trace Analyzer And CollectorApplication
Affected:< 2021.8.0

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. Check Intel Trace Analyzer and Collector version
    Run the version command for Intel Trace Analyzer, typically 'itte -version' or check the installed package/directory name containing 'intel' and 'trace analyzer'. On Linux, also check '/opt/intel/' directories or use package manager queries.
    Affected if Version is present but below 2021.8.0
  2. Check Intel OneAPI HPC Toolkit version
    Run the version command for the Intel OneAPI HPC Toolkit components, or check the installation directory under '/opt/intel/oneapi/' or 'C:\Program Files\Intel\oneapi\'. Look for hpc or itac related packages.
    Affected if Version is present but below 2023.0.0
  3. Verify if affected components are installed
    Search for traces of Intel Trace Analyzer (often installed as 'itac' or 'traceanalyzer') or Intel MPI products that bundle this tool. Check installed programs on Windows or use 'dpkg -l' / 'rpm -qa' on Linux.
    Affected if Neither product is installed, then the environment is not affected by this specific vulnerability

The environment is affected if Intel Trace Analyzer and Collector version is below 2021.8.0, or if Intel OneAPI HPC Toolkit version is below 2023.0.0, and either product is installed.

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.0 / 2023.0.0 or later
Fixed in 2021.8.02023.0.0
Interim mitigation

Upgrade Intel Trace Analyzer and Collector to version 2021.8.0 or later. Verify the upgrade in a test environment before production deployment due to the specialized nature of the software.

Recommended fix Moderate confidence

Intel Trace Analyzer and Collector 2021.8.0 or later; Intel OneAPI HPC Toolkit 2023.0.0 or later

  1. Identify currently installed versions of Intel Trace Analyzer and Collector and Intel OneAPI HPC Toolkit
  2. Download Intel Trace Analyzer and Collector version 2021.8.0 or later from the official Intel download repository
  3. Download Intel OneAPI HPC Toolkit version 2023.0.0 or later from the official Intel download repository
  4. Uninstall the vulnerable versions of both products
  5. Install the updated versions (2021.8.0+ for Trace Analyzer and Collector, 2023.0.0+ for OneAPI HPC Toolkit)
  6. Restart any running Intel software services
  7. Verify the installed versions using the software's version information or command-line tools

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

Fix this in Oneapi Hpc Toolkit 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-2023-23910 — 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-23910 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