CVE-2022-36384
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 · uneditedUnquoted 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 confidenceAn unquoted search path vulnerability exists in the installer software for Intel NUC Kit Wireless Adapter drivers on Windows 10 (versions before 22.40). When the installer executes binary files without proper path quoting, an attacker with authenticated local access can place a malicious executable in an intermediate directory path (e.g., under 'Program Files') that gets executed with elevated privileges during installation, achieving local 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.
-
Identify if Intel NUC wireless adapter software is installedCheck common installation directories for Intel NUC wireless adapter components: C:\Program Files\Intel\WiFi, C:\Program Files (x86)\Intel\WiFi, or search for files named 'IntelNUCWiFi*' or similar Intel wireless adapter installer files on the system.Affected if Intel NUC Kit Wireless Adapter Driver Installer files are found on the system before version 22.40.0
-
Check installed driver or installer versionRight-click on the installer executable, select Properties, then go to the Details tab to view the File Version. Alternatively, check the version of any installed Intel wireless adapter driver via Device Manager under Network adapters.Affected if The version number is lower than 22.40.0
-
Inspect installation paths for unquoted service pathsUse the command 'sc qc' or 'wmic service' to query services related to Intel wireless adapter installation. Examine if any service executable path contains spaces and is unquoted (e.g., C:\Program Files\Intel\WiFi\bin\something.exe).Affected if Service paths contain spaces (such as under Program Files) without quotes around the path
-
Verify the vulnerable installer binary exists in the exploitable pathSearch for installer executables (such as .exe files in the Intel wireless adapter installation directory) that would execute during installation. Check if these binaries reside in directories under 'Program Files' without proper path quoting.Affected if Installer binaries are located in paths like C:\Program Files\Intel\ that could be hijacked by placing a malicious executable in an intermediate directory
A system is affected if Intel NUC Kit Wireless Adapter Driver Installer version below 22.40.0 is present on Windows 10 and the installer uses unquoted paths containing spaces (such as Program Files directories) that could be exploited for local privilege escalation.
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 to version 22.40 or later, which contains a properly quoted search path in the installer. Organizations should review and remediate driver versions across managed endpoints.
22.40.0
- Download the Intel NUC Kit Wireless Adapter Driver Installer version 22.40.0 or later from the official Intel support website
- Verify the downloaded file integrity using provided checksums (if available)
- Run the installer with administrator privileges
- Follow the installation wizard prompts to complete the driver update
- Restart the system if prompted to ensure the new driver is properly loaded
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-36384 — 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-36384 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