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

CVE-2023-43751

MEDIUM · 6.7 CVSS v3.1 Published 2024-05-16
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 Intel(R) Graphics Command Center Service bundled in some Intel(R) Graphics Windows DCH driver software before versions 31.0.101.3790/31.0.101.2114 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 Graphics Command Center Service loads DLLs without using a fully qualified path, allowing an authenticated local attacker to place a malicious DLL in the search path and execute arbitrary code with elevated privileges.

MitigationUpdate Intel Graphics Windows DCH driver software to version 31.0.101.3790 or 31.0.101.2114 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.

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. Verify Intel Graphics Command Center Service is installed
    Open Services (services.msc) and look for 'Intel(R) Graphics Command Center Service' or run: sc queryex type= service state= all | findstr /i "Graphics Command Center"
    Affected if The service named 'Intel(R) Graphics Command Center Service' or similar Graphics Command Center service exists on the system
  2. Check if the service is running
    Run: sc query "IntelGraphicsCommandCenterService" or check the service status in Services.msc
    Affected if The service is in a running state, making it vulnerable to DLL hijacking while active
  3. Locate the service executable path
    Run: sc qc "IntelGraphicsCommandCenterService" and examine the BINARY_PATH_NAME, or use Process Explorer to find the running process path
    Affected if The executable path is in a writable directory or uses relative DLL loading
  4. Check Intel Graphics Command Center version
    Open Programs and Features (appwiz.cpl), find 'Intel Graphics Command Center', note the version; or check the driver version via: dxdiag -> Display tab -> look for driver version under the Intel GPU
    Affected if The installed version is earlier than 31.0.101.2114 or 31.0.101.3790 (or unknown/unlisted)
  5. Verify DLL search path vulnerability exists
    Use Process Monitor (ProcMon) to monitor the Intel Graphics Command Center Service process for DLL load attempts from writable directories, or manually inspect the service executable directory for weak permissions
    Affected if The service loads DLLs from directories with weak ACLs or does not use fully qualified paths for DLL loading

The system is affected if the Intel Graphics Command Center Service is installed, running, and the software version is earlier than 31.0.101.2114 or 31.0.101.3790, or if the service executable loads DLLs from directories with weak access controls.

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 Windows DCH driver software to version 31.0.101.3790 or 31.0.101.2114 or later to resolve the uncontrolled search path vulnerability.

Recommended fix High confidence

Intel Graphics Windows DCH driver version 31.0.101.3790 or 31.0.101.2114 (or later)

  1. Identify the current Intel Graphics Windows DCH driver version installed on the system
  2. Navigate to the official Intel website or Intel Driver & Support Assistant to obtain the updated driver
  3. Download Intel Graphics Windows DCH driver version 31.0.101.3790 or later (or 31.0.101.2114 or later for the alternate branch)
  4. Install the updated driver following Intel's standard installation procedure
  5. Restart the system to ensure the Graphics Command Center Service loads the updated components
  6. Verify the installed version matches or exceeds the fixed versions (31.0.101.3790 or 31.0.101.2114)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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