CVE-2021-0064
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 · uneditedInsecure inherited permissions in the Intel(R) PROSet/Wireless WiFi software installer 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 confidenceInsecure inherited permissions in the Intel(R) PROSet/Wireless WiFi software installer for Windows 10 prior to version 22.40 allows an authenticated local user to potentially escalate privileges. The vulnerability stems from improper permission inheritance in the installer component, enabling a local attacker to gain elevated access.
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< 22.40< 22.40< 22.40< 22.40< 22.40< 22.40< 22.40CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Confirm Intel PROSet/Wireless WiFi software is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs. Look for entries containing 'Intel PROSet' or 'Intel Wireless' in the name.Affected if Intel PROSet/Wireless WiFi software is present on the system
-
Check the installed Intel PROSet/Wireless WiFi software versionRun 'Get-ItemProperty "HKLM:\SOFTWARE\Intel\PlugPlay\Components\*" -ErrorAction SilentlyContinue | Where-Object {$_.DisplayName -like "*WiFi*"} | Select-Object DisplayName, ComponentVersion' in PowerShell, or right-click the WiFi adapter in Device Manager > Properties > Driver tab to view the driver version.Affected if The displayed version is earlier than 22.40
-
Identify the WiFi adapter firmware versionOpen Device Manager > Network adapters > Intel WiFi adapter > Properties > Advanced tab. Look for 'Firmware Version' or similar field. Alternatively, run 'netsh wlan show drivers' to see driver details.Affected if The adapter is one of: Intel Ax210, Ax201, Ax200, Ac 9560, Ac 9462, Ac 9461, Ac 9260, or Ac 8265 with firmware version prior to 22.40
-
Verify the vulnerability condition is metConfirm that Intel PROSet/Wireless WiFi software version is less than 22.40 AND the system has an affected Intel WiFi adapter model listed in the CVE. Check Program Files or Program Files (x86) for Intel folders and review installer component permissions if accessible.Affected if Both conditions are true: software version < 22.40 AND affected WiFi adapter firmware is present
A system is affected if Intel PROSet/Wireless WiFi software version is below 22.40 and the system uses one of the affected Intel WiFi adapters (Ax210, Ax201, Ax200, Ac 9560, Ac 9462, Ac 9461, Ac 9260, or Ac 8265) with firmware versions prior to 22.40.
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
Update Intel PROSet/Wireless WiFi software to version 22.40 or later to remediate the insecure permissions issue.
Intel PROSet/Wireless WiFi software version 22.40 or later
- Identify the current version of Intel(R) PROSet/Wireless WiFi software installed on the system
- Navigate to the official Intel download support page at www.intel.com to obtain the latest version
- Download Intel PROSet/Wireless WiFi software version 22.40 or later for Windows 10
- Run the installer with administrative privileges
- Follow the on-screen prompts to complete the installation
- Restart the system when prompted to ensure all components are properly updated
- Verify the installed version matches or exceeds 22.40 via the software interface or Windows Programs and Features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0064 — 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-2021-0064 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