CVE-2024-36245
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 · uneditedUncontrolled search path element in some Intel(R) VTune(TM) Profiler software before version 2024.2.0 may allow an authenticated 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 · high confidenceIntel VTune Profiler before version 2024.2.0 contains an uncontrolled search path element vulnerability, likely allowing DLL hijacking. An authenticated local user could place a malicious library in a directory searched by the application, resulting in privilege escalation when the application loads the rogue library.
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< 2024.2< 2024.2.0< 2024.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check Intel VTune Profiler versionLocate the vtune program directory (typically in C:\Program Files (x86)\Intel\oneAPI\vtune\ or C:\Program Files\Intel\oneAPI\vtune\). Right-click vtune.exe, select Properties, and view the File version in the Details tab. Alternatively, run 'vtune.exe --version' from the command line if available.Affected if The version number is lower than 2024.2.0 (for example, 2024.1, 2023.x, or earlier)
-
Verify the Intel oneAPI toolkit versionOpen Intel OneAPI Base Toolkit or Intel System Bring Up Toolkit installer (or check installed programs in Control Panel > Programs and Features). Look for the installed version in the program list.Affected if The installed toolkit version is listed as version 2024.1 or earlier, or shows a version without the 2024.2 designation
-
Inspect the application working directoryLaunch Intel VTune Profiler and note the directory from which it is executed. Check if the application is being run from a user-writable location such as a temp folder, downloads folder, or an unsecured network share.Affected if VTune Profiler is launched from a directory where an unprivileged user can write files (such as %TEMP%, Downloads, or a shared network path)
-
Review PATH environment variable for the userOpen Command Prompt and run 'echo %PATH%' to display the PATH variable. Check if any directories in the PATH are user-writable or untrusted locations (such as user home directories, temp folders, or publicly accessible network shares).Affected if The PATH contains user-controllable directories that appear before the Intel program directories, allowing a malicious DLL to be loaded first
-
Scan for unauthorized DLLs in VTune directoriesNavigate to the VTune Profiler bin directory (for example, C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\). List all .dll files and check for any unexpected or recently added DLLs that do not belong to the Intel installation.Affected if Unexpected DLL files are present in VTune directories, especially with timestamps matching recent dates or belonging to unknown applications
Your environment is affected if Intel VTune Profiler or the Intel oneAPI toolkit is installed at a version before 2024.2.0 AND the application is run from or has its PATH pointing to directories where untrusted users can place malicious DLL files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2024.22024.2.0
Upgrade Intel VTune Profiler to version 2024.2.0 or later. As a temporary workaround, ensure the application runs from trusted directories with controlled PATH variables and monitor for unauthorized DLL placement.
2024.2 (or 2024.2.0 for VTune Profiler)
- Identify the affected Intel software installed (OneAPI Base Toolkit, System Bring Up Toolkit, or VTune Profiler)
- Navigate to the official Intel download page or Intel.one portal
- Download the fixed version 2024.2 or later for your specific product
- Uninstall the current vulnerable version through Windows Settings > Apps or the Intel uninstaller
- Restart the system to clear any loaded DLLs from the old installation
- Install the new version 2024.2 or later by running the downloaded installer
- Verify the installed version matches or exceeds 2024.2
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36245 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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