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

CVE-2024-35245

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 element in some Intel(R) PROSet/Wireless WiFi software for Windows before version 23.60 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

This is a DLL hijacking/uncontrolled search path vulnerability in Intel PROSet/Wireless WiFi software for Windows. An authenticated user can place a malicious DLL in a directory that gets searched before the legitimate one, causing the application to load the attacker's code with elevated privileges when the WiFi software is launched.

MitigationUpdate Intel PROSet/Wireless WiFi software to version 23.60 or later. If immediate patching is not feasible, restrict write access to the software's installation directory and ensure only trusted paths are in the system PATH to prevent DLL preloading attacks.

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 PROSet/Wireless WiFi is installed
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed software.
    Affected if Intel PROSet/Wireless WiFi or Intel(R) PROSet/Wireless appears in the installed programs list
  2. Determine the installed version
    Check the version in Programs and Features, or query the registry key 'HKLM\SOFTWARE\Intel\PROSet\Wireless' for a Version value, or right-click the WiFi tray icon and select 'About Intel PROSet/Wireless'.
    Affected if The displayed version is below 23.60 (for example, 23.40, 23.30, 22.x, or earlier)
  3. Locate the installation directory
    Right-click the Intel PROSet/Wireless WiFi shortcut or tray icon, select 'Open file location' to find the executable path, typically under 'C:\Program Files\Intel\WiFi' or 'C:\Program Files (x86)\Intel\Wireless'.
    Affected if You can locate the installation folder containing the WiFi software binaries
  4. Check write permissions to the installation folder
    Right-click the installation folder, select Properties > Security, and verify which users have Write or Modify permissions. Alternatively, run 'icacls "C:\Program Files\Intel\WiFi"' in an elevated command prompt.
    Affected if Authenticated users or non-admin accounts have Write or Modify access to the Intel WiFi installation directory

You are affected if Intel PROSet/Wireless WiFi is installed and the installed version is below 23.60, AND users have write access to the software's installation directory where a malicious DLL could be placed.

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 PROSet/Wireless WiFi software to version 23.60 or later. If immediate patching is not feasible, restrict write access to the software's installation directory and ensure only trusted paths are in the system PATH to prevent DLL preloading attacks.

Recommended fix Moderate confidence

Intel PROSet/Wireless WiFi software version 23.60 or later

  1. Identify the current version of Intel(R) PROSet/Wireless WiFi software installed on the system
  2. Navigate to the official Intel support website or Intel Driver & Support Assistant
  3. Download Intel PROSet/Wireless WiFi software version 23.60 or later
  4. Run the installer and follow the on-screen instructions to apply the update
  5. Restart the system if prompted to complete the installation
  6. Verify the installed version matches or exceeds 23.60

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 / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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