dbcve.org
Oneapi Hpc ToolkitApplication · Intel

CVE-2022-42878

MEDIUM · 5.5 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 →
57/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
Null pointer dereference for some Intel(R) Trace Analyzer and Collector software before version 2021.8.0 published Dec 2022 may allow an authenticated user to potentially enable information disclosure 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

A null pointer dereference vulnerability exists in Intel Trace Analyzer and Collector software versions prior to 2021.8.0. An authenticated user with local access can trigger the null pointer dereference, potentially leading to information disclosure.

MitigationUpgrade Intel Trace Analyzer and Collector to version 2021.8.0 or later to address 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
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
None
Availability
None

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

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 if Intel Trace Analyzer is installed
    Search for the installation directory or check common install paths such as C:\Program Files\Intel\oneAPI\ or /opt/intel/oneapi/. Look for folders named 'vtune', 'trace-analyzer', or 'itac'. On Windows, check Add/Remove Programs. On Linux, run: find /opt -name '*trace*analyzer*' 2>/dev/null
    Affected if Intel Trace Analyzer and Collector software is found on the system
  2. Determine Intel Trace Analyzer version
    If installed, locate the version file or executable. Common locations: <install_dir>/itac/version.txt or run: <install_dir>/bin/itac -version. On Windows: C:\Program Files\Intel\oneAPI\itac\latest\bin\itac.exe -version
    Affected if The installed version is lower than 2021.8.0 (e.g., 2021.7.0, 2021.6.0, etc.)
  3. Check if Intel OneAPI HPC Toolkit is installed
    Search for the Intel OneAPI HPC Toolkit. On Windows, check Add/Remove Programs for 'Intel OneAPI HPC Toolkit'. On Linux, check /opt/intel/oneapi/ for hpc-platform or similar components. Run: ls /opt/intel/oneapi/ | grep -i hpc
    Affected if Intel OneAPI HPC Toolkit is found on the system
  4. Determine Intel OneAPI HPC Toolkit version
    Locate the version information in the installation directory or registry. Common path: C:\Program Files\Intel\oneAPI\hpc-toolkit\version.txt or check the installer metadata. On Linux: cat /opt/intel/oneapi/hpc-toolkit/version.txt 2>/dev/null
    Affected if The installed version is lower than 2023.0.0 and includes vulnerable Trace Analyzer components
  5. Verify local user authentication context
    Confirm that local user accounts exist on the system. On Windows: net user. On Linux: cat /etc/passwd. The vulnerability requires an authenticated local user to trigger the null pointer dereference.
    Affected if Local user accounts are present and the software versions listed above are vulnerable

A user is affected if Intel Trace Analyzer and Collector version is below 2021.8.0 OR Intel OneAPI HPC Toolkit version is below 2023.0.0, and local authenticated users can access the system.

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 to address this vulnerability.

Recommended fix Moderate confidence

Intel Trace Analyzer and Collector 2021.8.0 (or OneAPI HPC Toolkit 2023.0.0)

  1. Identify the installed Intel Trace Analyzer and Collector version using 'vtexpand --version' or checking the installation directory
  2. Download Intel Trace Analyzer and Collector version 2021.8.0 or later from the official Intel website
  3. Backup any existing trace data and project configurations before upgrading
  4. Uninstall the current version of Intel Trace Analyzer and Collector
  5. Install the updated version 2021.8.0 or later
  6. Verify the installation by running 'vtexpand --version' to confirm the new version
  7. If using OneAPI HPC Toolkit, ensure the toolkit is also upgraded to version 2023.0.0 or later

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

Fix this in Oneapi Hpc Toolkit Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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