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

CVE-2024-22376

MEDIUM · 6.7 CVSS v3.1 Published 2024-08-14
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 element in some installation software for Intel(R) Ethernet Adapter Driver Pack before version 28.3 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 · moderate confidence

This is a DLL hijacking vulnerability (uncontrolled search path element) in the Intel Ethernet Adapter Driver Pack installer versions prior to 28.3. The installer loads DLLs from an uncontrolled path, allowing an authenticated local user to place a malicious DLL that gets loaded during installation, leading to privilege escalation from the user's existing authenticated context.

MitigationUpdate Intel(R) Ethernet Adapter Driver Pack to version 28.3 or later. Prior to deployment, verify the update source integrity and test in a controlled environment to ensure network adapter functionality is not impacted.

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. Locate Intel Ethernet Adapter Driver Pack installation
    Open Windows Control Panel > Programs and Features, or use 'Get-WmiObject -Class Win32_Product' via PowerShell to enumerate installed software. Look for entries named 'Intel(R) Ethernet Adapter Driver Pack' or similar Intel network driver pack packages.
    Affected if The Intel Ethernet Adapter Driver Pack software appears in the installed programs list
  2. Retrieve the installed version number
    In Programs and Features, click on the Intel Ethernet Adapter Driver Pack entry and view the version column, or right-click and select Properties to view the Version field. If using PowerShell, query the Version property from the Win32_Product object.
    Affected if The version displayed is earlier than 28.3 (for example, 28.2.x, 28.1.x, or older)
  3. Verify installer executable version if available
    If you have the original installer executable file (.exe) used to deploy the driver pack, right-click the file in Windows Explorer, select Properties, and examine the File Version on the Details tab.
    Affected if The installer file version is earlier than 28.3

A user is affected if the installed Intel Ethernet Adapter Driver Pack version is less than 28.3, as the installer loads DLLs from an uncontrolled path allowing privilege escalation during installation.

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(R) Ethernet Adapter Driver Pack to version 28.3 or later. Prior to deployment, verify the update source integrity and test in a controlled environment to ensure network adapter functionality is not impacted.

Recommended fix Moderate confidence

Intel(R) Ethernet Adapter Driver Pack version 28.3 or later

  1. Identify the current version of Intel(R) Ethernet Adapter Driver Pack installed on the system
  2. Navigate to Intel's official support website and download Intel(R) Ethernet Adapter Driver Pack version 28.3 or later
  3. Verify the downloaded driver package matches the system architecture (x86/x64)
  4. Run the driver installer with administrative privileges
  5. Follow the on-screen installation wizard prompts to complete the update
  6. Restart the system as required by the installer to apply the new driver
Caveat Driver updates may require system restart; ensure compatibility with specific Ethernet adapter hardware before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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