dbcve.org
AdvisorApplication · Intel

CVE-2024-39284

MEDIUM · 6.7 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 2024.2 or later.
See remediation →
67/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
Uncontrolled search path for some Intel(R) Advisor software before version 2024.2 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 confidence

Intel Advisor before version 2024.2 contains an uncontrolled search path vulnerability that allows an authenticated local user to potentially escalate privileges by placing malicious code in a location the software loads from without proper path validation.

MitigationUpgrade Intel Advisor to version 2024.2 or later to resolve the uncontrolled search path 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:< 2024.2
Oneapi Base ToolkitApplication
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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Intel Advisor installation
    Search for the Intel Advisor application in standard installation directories: On Windows check 'Program Files (x86)\Intel\' or 'Program Files\Intel\', On Linux check '/opt/intel/oneapi/advisor/' or use 'whereis advisor' command
    Affected if Intel Advisor is found installed on the system
  2. Determine Intel Advisor version
    On Windows, right-click the advisor.exe file, select Properties, and check the 'Details' tab for Product Version. On Linux, run 'advisor --version' or check the version file in the installation directory
    Affected if The installed version is earlier than 2024.2 (e.g., 2024.1, 2023.x, etc.)
  3. Locate Intel OneAPI Base Toolkit installation
    Search for OneAPI components: On Windows check 'Program Files\Intel\oneapi\', On Linux check '/opt/intel/oneapi/'. Use 'dir oneapi' on Windows or 'ls /opt/intel/oneapi/' on Linux to list installed components
    Affected if Intel OneAPI Base Toolkit or its components are installed
  4. Check OneAPI Base Toolkit version
    Look for version information in the OneAPI installation directory, typically found in a version.txt file or by running 'oneapi-cli --version' if available, or check the installer metadata
    Affected if The OneAPI Base Toolkit version is earlier than 2024.2
  5. Compare against affected version range
    If Intel Advisor is installed, verify whether the version number is less than 2024.2 by comparing the major.minor version numerically
    Affected if Either Intel Advisor or Intel OneAPI Base Toolkit is installed with a version number lower than 2024.2

The system is affected if Intel Advisor or Intel OneAPI Base Toolkit is installed with any version prior to 2024.2, as the uncontrolled search path vulnerability allows local privilege escalation through malicious code loading without proper path validation.

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

Upgrade Intel Advisor to version 2024.2 or later to resolve the uncontrolled search path vulnerability.

Recommended fix High confidence

2024.2

  1. Verify current Intel Advisor and/or OneAPI Base Toolkit version installed
  2. Download Intel Advisor version 2024.2 or later from the official Intel download center
  3. If using OneAPI Base Toolkit, ensure it is also updated to version 2024.2 or later to receive the vulnerability fix
  4. Uninstall the current (vulnerable) version of Intel Advisor
  5. Install the updated version (2024.2 or later)
  6. Restart the system if prompted
  7. Verify the installed version is 2024.2 or later

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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