dbcve.org
Oneapi Base ToolkitApplication · Intel

CVE-2024-37027

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 2024.2 / 2024.2.0 or later.
See remediation →
61/100
Remediation priority · Elevated

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 Input validation in some Intel(R) VTune(TM) Profiler software before version 2024.2.0 may allow an authenticated user to potentially enable denial of service 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

Intel VTune Profiler versions before 2024.2.0 contain an improper input validation vulnerability that allows an authenticated local user to trigger a denial of service condition through specially crafted input.

MitigationUpgrade Intel VTune Profiler to version 2024.2.0 or later to obtain the patched 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 Base ToolkitApplication
Affected:< 2024.2
System Bring Up ToolkitApplication
Affected:< 2024.2.0
Vtune ProfilerApplication
Affected:< 2024.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
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/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. Verify if Intel VTune Profiler is installed
    On Windows, check C:\Program Files (x86)\Intel\VTune\ or C:\Program Files\Intel\VTune\ for the vtune.exe binary. On Linux, check /opt/intel/vtune/ or ~/intel/vtune/. Alternatively, search for 'vtune-gui' or 'vtune' executables in common installation directories.
    Affected if The software is present on the system.
  2. Determine the installed version of Intel VTune Profiler
    Run 'vtune --version' from the VTune installation directory, or right-click vtune.exe and select Properties > Details to view the File Version. On Linux, run 'vtune --version' or check the version file in the installation directory.
    Affected if The version number returned is lower than 2024.2.0 (for standalone VTune) or lower than 2024.2 (for OneAPI toolkit components).
  3. Check if Intel OneAPI Base Toolkit or System Bring Up Toolkit is installed
    Search for Intel OneAPI components in the system. On Windows, check the Windows Registry under HKLM\SOFTWARE\Intel\OneAPI for installed toolkits. On Linux, check /opt/intel/oneapi/ for toolkit directories.
    Affected if Either toolkit is installed and its version is below 2024.2.
  4. Verify the software is accessible to authenticated local users
    Confirm that non-privileged local users have execute access to the VTune Profiler binaries or that VTune is running as a service accessible to local users.
    Affected if Local authenticated users can access and execute VTune Profiler functionality.

A system is affected if Intel VTune Profiler, Intel OneAPI Base Toolkit, or Intel System Bring Up Toolkit is installed with a version lower than 2024.2.0, and local users have authenticated access to the software.

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 2024.2 / 2024.2.0 or later
Fixed in 2024.22024.2.0
Interim mitigation

Upgrade Intel VTune Profiler to version 2024.2.0 or later to obtain the patched software.

Recommended fix High confidence

2024.2.0 or later for VTune Profiler, 2024.2 for Oneapi Base Toolkit, 2024.2.0 for System Bring Up Toolkit

  1. 1. Download Intel VTune Profiler version 2024.2.0 or later from the official Intel download center
  2. 2. If using Oneapi Base Toolkit, download version 2024.2 or later
  3. 3. If using System Bring Up Toolkit, download version 2024.2.0 or later
  4. 4. Uninstall the current version or use the installer to upgrade to the new version
  5. 5. Verify the installation by checking the version number in the VTune Profiler UI or via command line: vtune --version
Caveat Upgrading major toolkit versions may require recompilation of projects or adjustment of build configurations; review release notes for compatibility notes

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

Fix this in Oneapi Base 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-2024-37027 — 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-2024-37027 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