CVE-2022-36380
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 · uneditedUncontrolled search path in the installer software for some Intel(r) NUC Kit Wireless Adapter drivers for Windows 10 before version 22.40 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 confidenceThis is a DLL hijacking/uncontrolled search path vulnerability in the installer software for Intel NUC Kit wireless adapter drivers. The installer does not properly validate the paths from which it loads DLLs or executables, allowing an authenticated local user to place malicious files in search paths that the installer will use, leading to privilege escalation.
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< 22.40.0CVSS 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
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Intel NUC Kit Wireless Adapter Driver InstallerSearch for the installer executable on the system. Check typical installation directories such as Program Files, Program Files (x86), or C:\Program Files\Intel. Use file explorer search or PowerShell command: Get-ChildItem -Path 'C:\Program Files*' -Recurse -Filter '*Intel*NUC*Wireless*Installer*' -ErrorAction SilentlyContinueAffected if The installer executable for Intel NUC Kit Wireless Adapter Driver is found on the system
-
Check installer versionRight-click the located installer executable (.exe or related DLL), select Properties, and view the Version tab to find the FileVersion or ProductVersion number. Alternatively, right-click and select 'Properties' then 'Details' to view version information.Affected if The version shown is below 22.40.0 (for example, 22.30.0, 21.x.x, or any version number less than 22.40.0)
-
Confirm the installer is the vulnerable componentVerify the installer is specifically the Intel NUC Kit Wireless Adapter Driver Installer by checking the product name in the executable properties under the 'General' or 'Details' tab. Ensure it is the wireless adapter driver installer and not a different Intel NUC component.Affected if The product is confirmed as Intel NUC Kit Wireless Adapter Driver Installer with version less than 22.40.0
A system is affected if the Intel NUC Kit Wireless Adapter Driver Installer version is lower than 22.40.0, since the installer contains the DLL hijacking vulnerability that can be triggered when the installer runs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped22.40.0
Update Intel NUC Kit Wireless Adapter drivers for Windows 10 to version 22.40 or later, which contains the fixed installer software.
22.40.0 or later
- Identify the current version of the Intel NUC Kit Wireless Adapter Driver Installer installed on the system
- Navigate to Intel's official support website or the specific Intel NUC driver download page
- Download the Intel NUC Kit Wireless Adapter Driver Installer version 22.40.0 or later for Windows 10
- Uninstall the current vulnerable version of the wireless adapter driver installer from the system
- Restart the system if prompted by the uninstaller
- Install the newly downloaded version 22.40.0 or later
- Restart the system if prompted after installation
- Verify the installed version matches 22.40.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36380 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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