dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-34028

MEDIUM · 6.7 CVSS v3.1 Published 2024-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 in some Intel(R) Graphics Offline Compiler for OpenCL(TM) Code software for Windows before version 2024.1.0.142, graphics driver 31.0.101.5445 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

Uncontrolled search path vulnerability in Intel Graphics Offline Compiler for OpenCL and graphics driver 31.0.101.5445 allows an authenticated local attacker to influence what DLLs the application loads, potentially executing arbitrary code and escalating privileges.

MitigationUpdate Intel Graphics Offline Compiler for OpenCL to version 2024.1.0.142 or later, and update the graphics driver beyond version 31.0.101.5445.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Identify Intel Graphics Offline Compiler for OpenCL version
    Check the installed version of 'Intel Graphics Offline Compiler for OpenCL' - typically found in Program Files/Intel or via 'Programs and Features' in Control Panel, or by running the compiler with a version flag if available
    Affected if Version is present and less than 2024.1.0.142
  2. Identify Intel graphics driver version
    Open Device Manager, expand 'Display adapters', right-click the Intel GPU, select 'Properties', go to the 'Driver' tab and note the Driver Version field
    Affected if Driver version is 31.0.101.5445 or earlier (the version string typically shows as 31.0.101.xxxx)
  3. Check if the compiler runs from a user-writable directory
    Examine the directory from which the Intel Graphics Offline Compiler for OpenCL is executed; verify that standard users cannot write to that directory or any parent directory in the search path
    Affected if The application is run from or has its executable located in a directory writable by non-privileged users, allowing DLL injection
  4. Verify DLL search order configuration
    Check if the application or system has Safe DLL Search Mode disabled (registry key HKLM\System\CurrentControlSet\Control\Session Manager\SafeDllSearchMode set to 0)
    Affected if Safe DLL Search Mode is disabled and the application runs from a user-controlled directory

User is affected if either the Intel Graphics Offline Compiler for OpenCL version is below 2024.1.0.142 OR the graphics driver version is 31.0.101.5445 or earlier, AND the application can load DLLs from user-controlled directories.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel Graphics Offline Compiler for OpenCL to version 2024.1.0.142 or later, and update the graphics driver beyond version 31.0.101.5445.

Recommended fix Moderate confidence

2024.1.0.142

  1. Navigate to the Intel website and locate the Intel Graphics Offline Compiler for OpenCL Code software for Windows
  2. Download version 2024.1.0.142 or later from Intel's official download center
  3. Verify the downloaded installer matches the official Intel checksum
  4. Run the installer with administrative privileges
  5. Follow the on-screen installation prompts to complete the update
  6. Restart the system if prompted to ensure the driver updates take effect

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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